FAQ: Scenarios

Why is Delete my only related action when I hover over a scenario?: With the Manage Scenario
permission, you can only review and delete the scenarios that other users created.
Why don't I see the Merge or Download Changes options for the scenario listed?: You don't have the Merge Scenarios
or Download Scenario Changes
permissions. You might also be viewing the scenarios that others created.
What changes in an existing scenario when someone changes the data in a base version?: In the scenario, we ignore changes to the base version that conflict with changes you have already made in your scenario. For data points that you haven't changed in your scenario, we bring in any changes made to the base version. These updates ensure that you can review the most recent data in the base version as you work on your scenario.
Does the scenario limit apply to each person for each version?: The scenario limit is 15 scenarios across all versions for each user.
What happens if copying all scenarios of cloned versions causes users to reach their scenario maximum?: We provide a message stating that we didn't clone the version. You have 2 options:
Click the
Move all scenarios
check box and try cloning the version again. Because you move the scenarios from the original version, users retain the same number of scenarios.
Leave both scenario check boxes clear to clone the version without the scenarios.
What happens to my scenario if someone locks the base version?: You can still make changes to your scenario even after someone locked the base version. You can also still create new scenarios with a locked base version. However, to merge the scenario into the base, you have to unlock the base version.
Why are some of the changes that I made in the scenario not in the base version after I merged?: We ignore changes to scenario data during merges when access rules have removed your access to the data locations. Example: You no longer have access to an account, then we don't merge any changes you made in the scenario for that account. In most cases, you can't retrieve those changes from the scenario after merging.
What happens if multiple users merge changes from their own scenarios into the same base version?: We save the latest merge. This process is similar to how we handle sheets. Many people can work on a sheet at once and we honor the latest save.
How can I undo merged changes to a base version?: Before you merge, you can download the scenario changes and save the Excel file before you merge. The Excel file includes the original values in the base version and the changes in the scenario. You can then manually enter the original values.
Or, you can clone the base version before you merge:

Clone the base version and copy all the data, but don't move or copy the scenarios.
Create a name that indicates that the new version is the copy as of the specific date.
Lock this copy to keep others from changing the data. You can keep the copied version as an original just in case you need it.
After you merge scenarios, create a variance report comparing the locked copy of the base version and the postmerge base version.
Check the impact of the merged data.
If satisfied, you can delete the copy. If not satisfied, you can delete the merged version and unlock the copy.
What happens when I share a report that includes a personal scenario?: We remove the data from the scenario for the other user.
How do scenarios affect the performance of the model?: Scenarios affect the performance much less than cloned versions do because we only store the scenario changes, as opposed to the contents of the entire version. We recommend that you follow these guidelines:

Don't exceed a total of 9,000 scenarios per instance.
When you want to include the scenarios in a cloned plan version, use the Move all Scenarios
option instead of the Copy all Scenarios
.
Upon merging, select the Delete all scenarios created for this base version after merging
check box.
Manage your scenarios and delete unused scenarios or old scenarios. You can use Download Changes to save a record of the scenario when necessary.
Monitor and manage scenarios when you have the Manage All Scenarios
permission. Example: Delete unused scenarios, scenarios for base versions that are no longer the current version, and scenarios for locked versions.
Should I Create Scenarios or New Versions?: Use scenarios to:
Test small batches of change, contained within a sheet, or in an account hierarchy.
Try out different changes that you plan to make within weeks, rather than months.
Make changes that affect a subset of the model. A good gauge is less than about 10,000 cells

Use versions for:
Bulk changes that require the use of imports, loaders, and APIs.
Changes that would likely affect an excess of 10,000 cells.