Depending on your permissions, you can copy, move, or duplicate data stages within an environment.
| Action | Permissions required |
|---|---|
| Moving a data stage |
Administrator user or regular user with Write permission to source location and Write + Create [stage] permissions to the destination. |
| Copying a data stage |
Administrator user or regular user with Read permission to source location and Write + Create [stage] permissions to the destination. |
| Duplicating a data stage | The same permissions as required for copying. |
Tip: When rearranging data stages, keep in mind that a data stage that has been set to inherit security from the parent can inherit different security settings when moved, copied, or duplicated.
Moving a data stage
- Select the Pipelines menu at the top of the page.
- Click the menu button to the right of the data stage that you want to move and select Move To.
- Use the Move To dialog to select the new location.
Copying a data stage
- Select the Pipelines menu at the top of the page.
- Click the menu button to the right of the data stage that you want to move and select Copy To.
- Use the Copy To dialog to select the location where a copy of the data stage will be created.
Notes
- Copying a data stage creates an independent copy of the selected item.
- Copying an executable data stage (analysis, data view, process model) does not copy the original stage's executions history. Newly copied executables will have ran zero times.
- Copying an external data store created from file will only copy the data store's definitions, not its data. A newly copied external data store created from file will be empty.
- Copying an analytic model does not copy child models. Newly copied analytic models will have zero child models.
- If copying to the same path or folder,
_Copy#will be automatically appended to a data stage's name. If copying to a new path or folder,_Copy#will not be appended. To avoid confusion, it is recommended that you give copies unique names. - References and usages: Newly copied data stages will reference and use the same data stages as originals. This means that caution is required when copying executable data stages. For example, if you copied an analysis and modified the copy's design but didn't change the data store output, you would end up with two analyses pushing to the same data store output. To avoid this situation, use the Duplicate function.
Duplicating a data stage
- Select the Pipelines menu at the top of the page.
- Click the menu button to the right of the data stage that you want to move and select Duplicate.
- Use the Duplicate Item dialog to create a duplicate of the data stage.
Notes
- Duplicating a data stage creates an independent copy of the selected item, and also gives you the option to copy data stages the selected item references or uses.
- This can be particularly helpful when you want to make a copy of a data stage and modify it without affecting the data stages it is connected to.
- For example, you could duplicate an analysis and its data store output so that you could modify your duplicate analysis and run it without affecting the original data store output.
- Bullet points 1-3 from the Copying a data stage section also apply to duplication.
- Duplication requires you to give the duplicate a unique name.