Merging Configurations from Customer and Application Update

Changes from Application Update Changes from Customer Result of the Merge on the Pivot Grid Object

Configurations from application development which do not require secondary merge.

For example, change in dimension aliases.

Configurations from customer which do not require secondary merge.

For example, updates the chart options.

The customer’s configurations are maintained in the target database. Application changes are not applied because the changes were not on merge-able objects.

Only the application fix is copied; the customer’s chart option configurations are maintained.

Configurations from application development which require secondary merge.

For example, adding a new dimension.

Configurations from customer which do not require secondary merge.

For example, updates the chart options.

The customer’s configurations are maintained and the application changes are applied.

Only the application fix is copied; the customer’s chart option configurations are maintained.

Configurations from application development which do not require secondary merge.

Configurations from customer which require a secondary merge.

The customer’s changes are preserved, but the application fixes are not applied because the customer configurations always have a higher priority.

Configurations from application development which do not require a secondary merge.

Customer does not make any change to the pivot grid model but the user personalizes the pivot grid views.

The customer personalizations are preserved but the application changes are not applied because they are part of a merge-able group where the target values have preference over the source.

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

  1. The compare process determines that there are changes in Pivot Grid chart options and aliases. These being a part of the merge-able groups for the Pivot Grid, target values are preserved by default.

  2. In the final compare, the target values for the merge-able attributes are preserved and displayed to the users.

  3. Customer accepts the fix and then initiates a copy process.

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