Release Behavior

The release behavior defines how new data versions are released to the production project. You may also preview a data version in a project without releasing it to production.

To change the release behavior:

  1. In a project, on the navigation bar, click Data > Data Categories.

  2. In the Data Categories room, click the Actions button  on the right side of the data category that is used to generate data versions for your solution, and then click Edit.

  3. In the Release tab, click the Release behavior list, and select one of the release behavior types described in the table below.
  4. Click Update.

The following table describes the types of release behavior.

Release behavior Description
Auto-release latest

This behavior functions differently for scheduled and ad-hoc jobs:

  • Scheduled jobs: The latest data version generated from a scheduled job is automatically released to production and email notifications are sent to the users specified in the mailing list. For more information, see Manage the Mailing List.

    Note: The Make new data versions available for production option must also be enabled. For more information, see Manage the availability of data versions in production.

  • Ad-hoc jobs: The latest data version generated by a job inside a project is automatically set as the active data version for the project. This allows you to preview the new data version without having to manually update it. To release the data version to production, you must publish the project. For more information, see Publish Project Changes.

You can optionally include a base project to ensure your project only uses data versions created by the specified project or those derived from its lineage. For more information, see Set the base project for your releases.

Manual release

Select a data version from the list of available data versions to change the data version for your project. If you publish the project to production, this behavior releases the selected data version to the production project. For more information, see Set the Data Version.

Note: If manual release is selected, new data versions generated from scheduled jobs are not automatically released to production. To update your data, you must manually select the new data version and publish the project each time.

Caution: Do not set manual releases to production at the admin level if multiple child tenants exist. When a manual release is published, its data version number is applied to all child tenants. Because data version numbers are unique to each tenant, this can cause deployment failures as child tenants attempt to load a data version that does not exist in their environment.
Custom release Define the data version to release if the version you want isn’t included in the Manual release list.

Example:  

data= 9005124