Write protection ensures that your source data doesn't get overwritten and stays accurate within Cube.
Managed in Scenario dimensions in the Web portal, scenarios can be updated with write protection based on the source and purpose of the data.
Let's explore the options.
Blocked
When a Scenario is blocked, no new data can be published to it from your spreadsheet or by importing data.
Changes to your data hierarchy, such as adding, disabling, or reordering dimensions or formulas or remapping dimensions to your source system, will change blocked scenarios.
Blocked scenarios will say "Blocked" in the Write Access column on the Scenario dimensions page.
For example:
Let's say it's the end of your fiscal year and you've finalized your annual budget. Now, you want to lock in that scenario so that no changes can be made to alter the data so that you can later compare how you performed to what was budgeted.
In Cube, you make a copy of your budget and apply write protection to lock it down:
Now, you can compare your blocked budget to your annual forecast.
Locked - Actuals
Actuals write protection ensures that you have a single source of truth when it comes to your data and transactions. It is required for any Actuals data coming from your source system, like a General Ledger.
This is partly because of how data is stored and accessed in the Cube, which ensures that data is well protected. Only Cube admins can publish to scenarios with Actuals write protection applied.
When configuring your Cube, the Cube Implementation team automatically applies this Actuals write protection to ensure healthy data transference.
Scenarios with Actuals write protection applied will say "Locked - Actuals" in the Write Access column on the Scenario dimensions page.