If you change either of these metadata elements, cube schema or hierarchy, you can use Model Resync to propagate the changes to any Essbase model that uses the metadata element. With Model Resync, you do not have to recreate models or re-configure any settings.
When you change a metadata element, Essbase Studio tags any model which uses the element as being out of sync with the latest version of the element. You can then choose to resync the model.
Events that trigger the need for a model resync include:
Cube schema changes:
Adding a hierarchy to the cube schema
Removing or replacing a hierarchy
Moving a hierarchy
Modifying a hierarchy
Renaming the schema
Hierarchy changes:
Adding a chain to the hierarchy
Removing or replacing a chain
Moving a chain
Modifying a chain
Renaming the hierarchy
When you start to change a metadata element, you will see a warning if the element is used in any Essbase models. You will also see a listing of all models which use the element. If you decide to continue the update, all models that become out of sync are denoted by this icon next to the model name in the Metadata Navigator: .
Note: | If you resync the model, the settings of the other, unchanged elements will retain their current values. All chains that are unchanged in a hierarchy will also retain their current settings. If any elements are renamed, all other elements will retain their current name. |