How to Update a Dimension Hierarchy Without Clearing a Model

You can add new rollup members, move or change rollup members, and also add new leaf members.

Data stored against roll-up members will be deleted when the user updates the hierarchy however leaf level members (Level 0) data available in the model will be retained as is and users need to re-calculate and re-aggregate the model after updating the dimension hierarchy to make the model available for analysis and reporting

To modify your hierarchy on a model that already has data in it, you must first lock the associated model to prevent modifications and data inputs to the model while the hierarchy is being changed.

To lock the model and modify the hierarchy:

1. Select the Model task and the Setup subtask.
2. Select the model and click the Lock Model action as shown below. Notice that the status changed from Generated to Locked.
   Examples of locked and unlocked models:
   Note:

   If you do not lock the model, you will not be able to make changes to the hierarchy on a model which has data.
   
3. Select the Model task and the Dimension subtask. Notice the model has a status of Locked and the Action is Update.
   
4. Add, move, and delete rollup members. In this example, the 2010 member is moved from US Operations to Domestic Distribution Centers.
   Tip:

   to move a member to another parent, use cut and paste and change the Member Parent.

   Prior to move:

   

   After member has been moved:

   

   Important

   When moving hierarchical members from one parent to another, make sure you update the Member Parent. In the image above, the 2010 member had a US Operations parent. Since it was moved under the Domestic Distribution Center parent, the Member Parent name was changed.
5. Click Save. The following message displays.
   
6. Click Yes to continue. The following message displays.
   
7. Click OK and check your email to ensure the process is completed.
8. Select the Model task and the Setup subtask.
9. Ensure the model is selected and click Unlock Model. Notice that the Status is updated from Locked to Generated.
   
10. Select the Model task and the Calculation subtask.
11. Run the Aggregation type as well as any other calculations to make the model available for analysis and reporting. An example is shown below.
    
12. Click Run.
13. Once the Run Status is Complete, your views and reports are updated. In the view example below, notice that 2010 is now under the Domestic Distribution Centers rollup.

Best Practices for Updating the Hierarchy on a Model With Data

• Update one dimension hierarchy at a time. So, when a user updates the hierarchy a process will run in the background to clear the rollup data and retain the leaf level data and finally update the dimension hierarchy. The user will receive the email notification after the process is complete, so the recommendation is to wait until the email notification is received before updating another dimension of the same model.
• While the hierarchy is being updated, if a user tries to refresh the dimension hierarchy screen the latest changes made to the hierarchy may not be displayed. The user will see the changes made once the email notification is received indicating that the update hierarchy process is complete.
• Users should not try to unlock a model while the hierarchy is being updated. Only unlock a model once the email notification is received indicating that the update hierarchy process is complete.
• Run the Model > Validation after the update hierarchy process is complete.
• For adding new members, it is recommended to continue to use the ‘Append’ action available in the Dimension Hierarchy screen.

How Hierarchy Updates Affect Rollup Data

The following are the conditions under which Rollup Data will be affected:

• Spotlight Web
  When you update the Hierarchy in a generated model, certain actions like Delete member, Change member parent, and Change member rollup operator are unavailable. However, if you perform these actions while the model is locked, the Rollup Data will be deleted, and aggregation will not run.
  
• SpotlightXL (Versioned Hierarchy Management [Feature Flag] set to false)
  If you perform an Append operation with a versioned hierarchy, whether the model is generated or locked, Rollup Data will remain unaffected. However, if you perform a Delete operation when the model is locked, Rollup Data will be deleted, and aggregation will not run. Additionally, when you update the Hierarchy while the model is locked, the Rollup Data will be deleted, and aggregation will not run, even if you have only added new members.
  
  
• SpotlightXL (Versioned Hierarchy Management [Feature Flag] set to true)
  When you update the Hierarchy in a generated model, actions, like Delete member, Change member parent, and Change member rollup operator will delete the Rollup Data. Furthermore, the Restore Rollup Data calculation selected in the Model > Setup screen, will be executed. Similarly, if the model is locked, performing these same actions will delete Rollup Data, and the Restore Rollup Data calculation selected in the Model > Setup screen will run.