Merging Configurations from Application Development and User Personalizations

Changes from Application Update	Changes from Customer	Result of the Merge on the Pivot Grid Object
Configurations from application development which require secondary merge. For example, adds a new dimension.	Customer does not make any change to the pivot grid model but the user personalizes the pivot grid views.	Customized personalizations are preserved, and the application changes are applied to the view that is associated with the Pivot Grid model.

After the instance level compare of the merge-able objects:

1. No changes related to merge-able groups or secondary merge is found.

2. The compare process is repeated, and the system displays the compare report visualization to the user. The personalizations do not appear in the compare report but it shows a new dimension added to the pivot grid model.

3. Customer selects to uptake the fixes and initiates a copy.

4. The same merge framework is run to preserve the customer configuration.