When attempting to archive a scenario, you may find the option unavailable or encounter an error. This typically happens because the scenario is still linked to other items in the system.
Overview
When you try to archive a scenario and the option is unavailable or you receive an error, it’s usually because the scenario is linked to another scenario or object in Catalyst.
Common dependencies that can prevent archiving include:
| Dependency Type | Examples | Why It Prevents Archiving | Typical Resolution |
|---|---|---|---|
| Other Scenarios | Archived or active scenarios linked to your target scenario | Archiving removes access to linked data | Unarchive & delete dependent scenarios, then archive your target scenario |
| Actuals Scenarios | Financial actuals used in cubes/reports | Data linkage prevents removal | Edit dependent scenario to remove links |
| Pro Forma Scenarios | Forecast or planning scenarios referencing your scenario | Maintains projection integrity | Edit dependent scenario to remove links |
| Smartload Cubes | Data integrations that reference the scenario | Often part of automation and cannot be altered without breaking the integration | Cannot be removed; use the general performance workaround below |
Any of these dependencies can prevent a scenario from being archived.
Why This Happens
The system is designed to prevent archiving scenarios that have active or dependent links to other data sources or scenarios. This ensures data integrity and prevents broken references in cubes, reports, and planning tools.
How to Resolve: Dependent Archived Scenarios
If your target scenario is used in another scenario that is already archived (and hidden):
Identify the dependent archived scenarios (support/admin can help surface these).
Unarchive the dependent scenarios.
Delete each dependent scenario.
Archive your target scenario.
Note: Archiving and deleting scenarios both trigger cube rebuilds, which can take time. Perform these actions during low-activity periods.
How to Resolve: Other Dependency Types
Actuals or Pro Forma scenario dependencies:
You can edit or delete the dependent scenario to remove links to the scenario you want to archive.
Smartload cube dependencies:
These are often tied directly to integrations and typically can’t be altered without breaking the integration.
General Performance Workaround
If you cannot remove the dependency but still want to improve processing performance, you can:
Edit the scenario you want to archive.
Deselect Show in Cube, Reports, and Planning.
This effectively removes the scenario from active processing, greatly improving performance, even though it will still appear in the Manage Scenarios list.
Future Improvements
We’ve submitted a request to make this process more user-friendly and reduce the number of steps needed to archive dependent scenarios.
Scenario archiving is often blocked by hidden or active dependencies, which can include other scenarios, actuals, pro forma, or Smartload cubes. By identifying and addressing these dependencies—or applying the “soft archive” method—you can maintain clean processing and faster performance until a more streamlined solution is released.
Comments
0 comments
Article is closed for comments.