Duplicating an Application can be useful, but it’s important to assess whether it’s truly necessary. When you duplicate an Application, you also duplicate its data and create new references on shared Blocks, which increases storage usage and can impact performance.
If the original Application references another Application—such as an OPEX Application referencing a Data Hub—the duplicate retains this connection. If you need the new Application to function independently, you must manually disconnect it from the original reference.
To optimize storage and system efficiency, ensure that you don’t keep any duplicated Applications longer than necessary.
Before you begin
To ensure a smooth and error-free duplication process, we recommend the following best practices:
- Resolve outstanding errors first. Fix any errors in the Application to avoid carrying them into the duplicated Application.
- Review access rights. Since access rights are duplicated exactly, review them and adjust them if necessary.
- Understand import configurations. Import configurations are also duplicated, meaning that future imports in the new Application impact its dependencies just like in the original Application.
- Consider Snapshots for as a fail-safe. If you need a fixed image of your Application, consider creating a Snapshot instead of duplicating it. Snapshots are stored within the Application, however they have specific limitations. Your Snapshot limit depends on your specific subscription plan.
For more information, see Application Snapshot Limits. - Handle failed duplications properly. If the duplication fails, wait a moment and try again. If it still doesn’t work, contact Pigment Support with the Application name and timestamps of both attempts.
- Check permissions. Only Members with the Display Application permission can duplicate Applications.
Duplicate an Application
Do the following:
- Go to the Workspace homepage.
- Locate the required Application and click the three dot menu (…).
- Select Duplicate.