EducationSoftwareStrategy.com
StrategyCommunity

Knowledge Base

Product

Community

Knowledge Base

TopicsBrowse ArticlesDeveloper Zone

Product

Download SoftwareProduct DocumentationSecurity Hub

Education

Tutorial VideosSolution GalleryEducation courses

Community

GuidelinesGrandmastersEvents
x_social-icon_white.svglinkedin_social-icon_white.svg
Strategy logoCommunity

© Strategy Inc. All Rights Reserved.

LegalTerms of UsePrivacy Policy
  1. Home
  2. Topics

KB18429: Overview of Project Merge conflict resolution in MicroStrategy Object Manager 10.x


Community Admin

• Strategy


KB18429: Overview of Project Merge conflict resolution in MicroStrategy Object Manager 10.x

Strategy Project Merge is a tool that allows users to perform object migration between projects.
 
Project Merge allows users to synchronize a large number of objects between projects.
 
Project Merge logic works based on IDs as any other Strategy Administrator tool. Project Merge checks the destination project for the existence of every object in the source project, by ID.
 
The resulting possibilities are:
 

  1. If an object ID does not exist in the destination project; the object is copied from the source project to the destination project.
  2. If an object exists in the destination project and has the same object ID and version in both projects, the objects are identical and a copy is not performed.
  3. If an object exists in the destination project and has the same object ID in both projects but a different version, there is a conflict that must be resolved. The conflict is resolved by following a specified rule.

The conflict resolution rules can be:
 

  • Use existing: No change is made to the destination object.
  • Replace: The destination object is replaced with the source object.
  • Keep both: No change is made to the destination object. The source object is duplicated in the destination location.
  • Use newer: If the source object's modification time is more recent than the destination object's, the Replace action is used. Otherwise, the Use existing action is used.
  • Use older: If the source object's modification time is more recent than the destination object's, the Use existing action is used. Otherwise, the Replace action is used.

Users can find more information related to Project Merge and the set of rules in the System Administration Guide in the Product Manuals.
 


Comment

0 comments

Details

Knowledge Article

Published:

June 5, 2017

Last Updated:

June 5, 2017