Merging Customer Changes on Delivered Pivot Grid Objects

Changes from Application Update	Changes from Customer	Result of the Merge on the Pivot Grid Object
Update from application development on the pivot grid model and related objects. For example, changes to the query that is associated with the Pivot Grid model.	Configurations from customer which do not require secondary merge. For example, updates the chart options.	No merge is performed. If the customer selects to copy over the new version, all personalizations for the model need to be removed.
Updates from application development on the pivot grid model and related objects.	Configurations from customer which require a secondary merge.	No merge is performed because customizations are detected. If customer decides to upgrade, the behavior is the same as in the previous PeopleTools releases (that is earlier than PeopleTools 8.54) where the source definition replaces the existing target definition.
Configurations from application development which do not require a secondary merge.	Customization from customer on the Pivot Grid model.	No merge is performed because customizations are detected. If customer decides to upgrade, the behavior is the same as in the previous PeopleTools releases (that is earlier than PeopleTools 8.54) where the source definition replaces the existing target definition.
Configurations from application development which require secondary merge.	Customization from customer on the Pivot Grid model.	No merge is performed because customizations are detected. If customer decides to upgrade, the behavior is the same as in the previous PeopleTools releases (that is earlier than PeopleTools 8.54) where the source definition replaces the existing target definition.
Updates from application development on the pivot grid model and related objects.	Customization from customer on the Pivot Grid model.	No merge is performed because customizations are detected. If customer decides to upgrade, the behavior is the same as in the previous PeopleTools releases (that is earlier than PeopleTools 8.54) where the source definition replaces the existing target definition.
Updates from application development on the pivot grid model and related objects.	Customer does not make any change to the pivot grid model but the user personalizes the pivot grid views.	All personalizations are removed.

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

1. The Pivot Grid custom merge code detects the customization and updates.

2. The updates including customizations are logged, and the merge process aborts.

3. A compare process is repeated, and the system displays the compare report visualization to the user. All changes, like the query name change, are listed in the compare report.

4. Customer can either select to retain the existing Pivot Grid model or copy over the new one.

5. An upgrade is run based on the customer’s selection.