This article describes how to bring in changes from concurrent users of the same profile version.
In this article:
In a locked profile, only one user is allowed to modify a version at any given time. But in the case of an unlocked profile, several users are able to make changes in the same version at the same time. In the event that one of them saves or publishes their version first, the remaining concurrent users are alerted to the new change.
In this event, the remaining users have the opportunity to salvage any changes they made in that version before it was overwritten. This is made possible by Merge Changes, a feature built into Tealium iQ for resolving concurrent user situations. This feature is automatically invoked the instant it detects a combination of saved and unsaved changes inside the same version. It then allows concurrent users to merge their unsaved changes with the saved changes in order to keep from losing their efforts.
The Merge Changes feature does not support Profile Inheritance (Libraries).
In this scenario, User A is editing a certain Version X and overwrites it with Save/Publish just when User B is also editing it. Version X now has a new revision, along with unsaved changes. What can User B do to salvage their changes? There are two options:
The "new revision" alert message in your version is a cue for you to take action. To bring concurrent changes into your version,
Concurrent users will not see your new version unless they refresh their Tealium iQ session.
If you decide to keep your changes only and discard the other user's changes, your best best is to perform a Save As without merging. To do that:
Because you are not merging anything, you will NOT be presented the list of saved changes.
Conflicts arise when you to attempt to merge the saved and unsaved instances of the same Tealium iQ element. This is typically the case when the element is modified by several users at the same time. For example, a certain Load Rule condition with a date range will conflict and collide with same Load Rule condition without a date range. Merging the two Load Rules is not possible unless you accept one instance and discard the other.
To resolve a conflict from the Merge Changes window:
Not able to merge? The merging operation may fail if the user lacks certain permissions in the account, or when linked libraries are present in the version. More details are available in the troubleshooting guide.