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

KB42424: How to replace an object through MicroStrategy Object Manager even though the conflict resolution says the objects exist identically?


Community Admin

• Strategy


This knowledge base article explains how to replace an object through MicroStrategy Object Manager even though the conflict resolution says the objects exist identically.

When creating a package within Strategy Object Manager,  the user is allowed to choose the 'Force Replace' option for the Action.  What this option does is that it migrates the object even if it exists identically in the source project.  Choosing the 'Replace' option will only migrate an object is the version IDs are different.
 

ka0PW00000010afYAA_0EM440000002Cws.png

 
Some reasons to use the Force Replace option are:
-To try and write over an inconsistent object in the destination project that appears to exist identically.
-To try and change the modification time of objects in the destination folder even though objects exist identically.
-If a migration occurred and certain package options were not properly set (i.e ACL options), and then users tried to remigrate, the 'Force Replace' option should be set to force the objects to move over.


Comment

0 comments

Details

Knowledge Article

Published:

May 11, 2017

Last Updated:

February 27, 2024