Export a Formula or Data Set

When creating a package to be exported from the current environment to another environment, you may need to select the formula version to be included in the deployment package, regardless of its status:

  • draft
  • active
  • closed.

The following checks are performed when deploying a package containing a formula from one environment to another:

  • The system checks the formula name, to see if there are any matches on the deployment environment. If a formula with the same name exists on the deployment environment, then its input parameter and output formula steps are checked and, if they are identical with those on the package to be imported, then the system concludes the formula to be imported is an update to the one found on the environment, and the formula to be deployed becomes the latest version of the existing formula.
  • On the deployment environment, the system checks if the existing formula has a draft version. If there is an existing draft version, the system displays an error message on importing the package. The user must then remove or delete the draft version in order to deploy/import the formula from the package.
    • If there is no draft version, the deployed formula is imported with Draft status, with the start date set as the current date if the start date is earlier than the current date. All links of parent formula and master formula are reinitialized.
  • If the input and output parameters are different from the package formula, the formula is imported as a new one with the name changed to name_importdate.
    • If the name differs, then the formula is imported as a new one, in Draft status, version 1, with the start date the same as the current date.

  • VersionStamp ID is updated when reexporting a package that received a change. For example, a package with a formula is exported from one environment with v22.1.10 and imported on another environment with v22.1.9.3. The package has a certain VersionStamp ID. When a change is made on v22.1.10 and the package is reimported on v22.1.9.3, the VersionStamp ID changes. This way, you can see that the package received a change before being reimported on the destination environment.