How Does Microstrategy Object Manager Determine If Two Objects In Dif

1.	How Does Microstrategy Object Manager Determine If Two Objects In Different Projects Are The Same?
Answer» To determine if two OBJECTS are the same, MICROSTRATEGY Object Manager COMPARES their Object ID's. If these ID's are the same, MicroStrategy Object Manager then compares the Version ID's. If the Version ID's are the same, the Conflict Resolution GRID lists the conflict as 'Exists Identically.' If the Version ID's are DIFFERENT, the Conflict Resolution grid lists the conflict as 'Exists Differently. To determine if two objects are the same, MicroStrategy Object Manager compares their Object ID's. If these ID's are the same, MicroStrategy Object Manager then compares the Version ID's. If the Version ID's are the same, the Conflict Resolution grid lists the conflict as 'Exists Identically.' If the Version ID's are different, the Conflict Resolution grid lists the conflict as 'Exists Differently.

How Does Microstrategy Object Manager Determine If Two Objects In Different Projects Are The Same?

Answer»

To determine if two OBJECTS are the same, MICROSTRATEGY Object Manager COMPARES their Object ID's. If these ID's are the same, MicroStrategy Object Manager then compares the Version ID's. If the Version ID's are the same, the Conflict Resolution GRID lists the conflict as 'Exists Identically.' If the Version ID's are DIFFERENT, the Conflict Resolution grid lists the conflict as 'Exists Differently.

To determine if two objects are the same, MicroStrategy Object Manager compares their Object ID's. If these ID's are the same, MicroStrategy Object Manager then compares the Version ID's. If the Version ID's are the same, the Conflict Resolution grid lists the conflict as 'Exists Identically.' If the Version ID's are different, the Conflict Resolution grid lists the conflict as 'Exists Differently.

Discussion

No Comment Found

Related InterviewSolutions

What Is A Materialized View?
How To Reduce Multiple Passes To One In A Report?
I Have A Fact Table At All Time Levels(date, Week...year). I Have The Similar Fact Table At Year Level. If I Create A Report With A Fact Attribute And A Metric Based On That Fact........ How Do We Force The Mstr To Use Year Level Fact Table Instead Of Using The All-levels Fact Table?
If We Need To Restrict Certain Columns From Appearing To A User/user-group How Can We Do It?
If We Need To Restrict Certain Rows From Appearing To A User/user-group How Can We Do It?
How Do We Prevent A Cross-join?
What Leads To A Cross-join Or How Does A Cross-join Occur?
When Do We Need To Create A View Or A Materialized View In A Database?
What Kind Of Optimizations You Did?
How Can Users Design Dashboards Quickly And Without Programming Experience Or Training?