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

KB5882: What are the different actions available for conflict resolution of objects in MicroStrategy Administrator - Object Manager?


Community Admin

• Strategy


The Conflict Resolution Window allows users to decide the appropriate action to take when an object already exists in the destination project. The action options provided to resolve object conflicts depend on the object type.

The Conflict Resolution Window allows users to decide the appropriate action to take when an object already exists in the destination project. The action options provided to resolve object conflicts depend on the object type.
 
For Application and schema objects, the action options are :
 

  • Use Existing: The destination object remains the same.
  • Keep Both: The destination object remains the same. Strategy Object Manager creates a duplicate of the source object in the specified destination location. You can provide a new name for the duplicate object.
  • Replace: The source object replaces the destination object. If the source and destination objects are identical except for path (the source object was moved), this option changes the path of the destination object to match the path of the source object.
  • Use Newer: If the source object is newer than the destination object, a Replace action occurs. If the source object is older than the destination object, a Use Existing action occurs.
  • Use Older: If the source object is newer than the destination object, a Use Existing action occurs. If the source object is older than the destination object, a Replace action occurs.

For Database Instances and Schedules, the action options are the same as with application and schema object conflicts:

  1. Use Existing
  2. Keep Both
  3. Replace
  4. Use Newer
  5. Use Older
  • Database Instances and Schedules can only be copied into their respective folders.
  • Events are copied with the Schedule to which they relate.
  • Strategy connection layers - Data Source Names, Database Logins and Database Connections -are copied with the Database Instance to which they belong. (Note that this does not mean that the actual ODBC DSN is copied - this may need to be created separately).

 
For Users and User Groups, the possible action options for conflict resolution include:

  • Use Existing
  • Replace
  • Merge Memberships: Applies only to users and groups. Strategy Object Manager modifies the membership information of the destination user/group so that it reflects the current content of the source and destination user/group, if it is not currently included in the destination user/group memberships.

 


Comment

0 comments

Details

Knowledge Article

Published:

June 14, 2017

Last Updated:

June 14, 2017