This article shows how to use the merge feature to combine changes from two versions of your iQ profile.
The "Merge changes into current session" feature comes in handy when you have to bring changes from an old version into the currently-published version. It could be that you were testing the old version in Dev or QA environments and it is finally ready to be merged into the Prod environment. Using this built-in feature you can handpick older changes, merge them in the current version, and continue to save/publish as usual.
This feature does not support Profile Inheritance (Libraries).
Enabling this checkbox in the Versions tab lights up the origin path, showing how each version is related to the other versions in the publish history. Why is it important? The origin path is your visual guide for determining which versions you can or cannot merge.
Two versions can be merged only if they have branched away from the same origin or ancestor. What does this mean? Take a moment to trace the path of publish history in your profile. You will notice that saved (overwritten) versions have lined up in the same origin path whereas saved-as versions have branched away into distinct paths. Merging is possible only when the versions--current and incoming--are present in distinct paths.
Here's a sample publish history with the #2 as the current version.
As you can see,
Make sure that the incoming and current versions are in distinct origin paths.Drop down the arrow next to the incoming version and click on "Merge changes into current session".
Watch a quick video tutorial on how to merge changes between concurrent users:
Here's another quick video tutorial on how to merge changes between versions:
Conflicts arise if the versions contain two distinct instances of the same Tealium iQ element. For example, a certain Load Rule condition with a date range in the old version will conflict and collide with same Load Rule condition without a date range in the current version. Merging them is not possible unless you accept one instance of the element and discard the other.
To resolve a conflict from the Merge Changes window,
The following are common errors, and their solutions:
This message informs you that the version cannot be merged because it is lined up in the same origin path as the current version. (how is the origin path related to merging?) You will notice this message for other versions that are also lined up in the same path.
Solution: Make sure that the current and incoming versions belong to distinct origin paths. (More details in Merge-into-current-session.)
This message appears when you attempt to merge any unsaved or pending changes, whether they are in the current or incoming versions.
Solution: Save/Publish the version in question before proceeding to merge.
This alert informs you that the merge operation has failed due to one or more reasons. Here are the possibilities:
This indicates that certain changes are secured by Resource Locks. You cannot perform the merge operation unless you have the required permissions to access or edit any resource locks. This error may occur when merging between versions or between concurrent users.
Solution: Make sure you are granted the "Manage Resource locks" permission by your account admin.
This informs you that one of the versions, either current or incoming, is still linked to a library. This scenario may occur when you attempt to merge between versions. Remember-merging is NOT supported for linked libraries.
Solution: Make sure to unlink the libraries from both current and incoming versions. To do that, go to Account Admin >> Manage Profiles and click "Remove" next to the library that needs to be unlinked.
Solution: Contact your Account Manager for further assistance.