When executable data stages are promoted, they need to be executed in their new environment in order to be repopulated with data.
| Data stage | Details |
|---|---|
| Analysis | Analyses containing data store outputs need to be executed upon promotion in order to load their outputs with data. Until a newly promoted analysis is executed, any other promoted data stages that depend upon its output will not function. |
| Data view |
Newly promoted data views will not contain any data and cannot be used to visualize until they are executed in the new environment. Additionally, any newly promoted dashboard that uses a newly promoted data view will not display any information until the data view has been executed. |
| Data store |
If a data store was created by uploading a file to Data360 DQ+ in one environment and this data store is promoted to another environment, the data store will be empty in the new environment. To repopulate the data store, the original file that was used to create it needs to be uploaded in the new environment. This applies to data stores that are of the external type which feature an Upload File button when being edited. All other data store types retain their data during promotion. |
Execution of a newly promoted data stage can be performed manually, scheduled, or built into a pipeline using process models that you promote along with your executable data stages, see Executing data stages.
Managing environment schedule settings
As an administrator, you can determine what should happen in a given environment when a data stage with scheduling enabled is promoted to that environment.
- From the menu at the top of the page, select Admin > Environments.
- Select one of the following options to determine what will happen when scheduled items are promoted to the selected environment:
- Never Create or Update - Scheduling information will not be created in that environment. As it will not be created, it will not be updated either.
- Always Create or Update - Scheduling information will be created in that environment and updated if it is ever changed in the source environment. This setting makes scheduling uniform between environments.
- Create but never Update - Scheduling information will be created in that environment, but it will not be updated if it is ever changed in the source environment.