Customizations Versus Configurations

When you run the process to preserve the configurations and personalizations, use this table as a guide for recognizing the type of modification and if the merge process is valid for the listed use cases.

Use Case	Type of Modification	Will merge retain the changes?
Updating Pivot Grid details: Pivot Grid title, Pivot Grid long description, and Pivot Grid owner ID.	Configuration	No
Updating Pivot Grid type to Public or Private.	Configuration	No
Adding a new dimension or fact.	Configuration	Yes
Updating a dimension or fact attribute: changing aliases, adding totals or total names, and changing aggregate functions for facts.	Configuration	No
Changing prompt values	Configuration	No
Changing display type to Pivot Chart Only, Grid Only, or Pivot Chart and Grid.	Configuration	Yes
Changing the view options for a Pivot Grid model that has the default view set to Pivot Grid and Chart.	Configuration	Yes
Changing the chart options.	Configuration	No
Changing the grid options.	Configuration	No
Changing the viewer display options.	Configuration	No
Adding a new related action on a new or existing axis.	Configuration	Yes
Marking a related action on an axis as inactive.	Configuration	No From a Pivot grid perspective, a related content ADS instance needs a merge.
Changing the menu layout for existing actions.	Configuration	No From a Pivot grid perspective, a related content ADS instance needs a merge.
Defining layout for a new or existing fact.	Configuration	No From a Pivot grid perspective, a related content ADS instance needs a merge.
Changing actions for a detailed view.	Configuration	No From a Pivot grid perspective, a related content ADS instance needs a merge.
Updating query name for a Pivot Grid model.	Customization	N/A
Changing a field type from dimension to fact or display column, or vice versa.	Customization	N/A
Removing a dimension or fact.	Customization	N/A