- TLC Home Home
- Discussions Discussions
- Documentation Documentation
- Knowledge Base Knowledge Base
- Education Education
- Blog Blog
- Support Desk Support Desk
02-15-2017 08:31 AM - edited 02-15-2017 08:34 AM
Imagine there is a profile linked to a library. Loading that profile always inherits the latest changes to the library. You publish the profile with the inherited changes. So far, so good.
Now something is wrong with that profile you just published and you need to perform a rollback. My understanding is that a rollback is done by publishing an earlier version. Please correct me if I am wrong here.
So you go to the "Versions" tab and load the previous version by selecting it and clicking on "Switch to this version".
You notice with a slight shiver that the previous version is inheriting the same, latest library version. Not what you wanted! ;-)
Theoretically, you'd need to go back to the library, publish the version that was active when your profile was last published and then publish again. Often, this is not only cumbersome but can get very messy because other profiles will be inheriting the same (old) library.
My question therefore: Is there a safer and more convenient way to achieve what I just described?
Solved! Go to Solution.
02-15-2017 10:50 AM - last edited on 02-15-2017 11:27 AM by kathleen
@jmbolfing have you considered just reverting the library to 'qa' and then only linking the one profile to update from 'qa'? Usually they are linked to 'prod' by default, but you can change this for this one publish and then switch back to linking to 'prod' afterwards.
Thanks very much for sharing your idea. That sounds indeed like a more convenient way.
However, I think it would be great if Tealium by default does not inherit library changes. The user would have to actively request the changes to be inherited (with a click on something like a "inherit library" button). That of course as a feature request.
But I'll work with your suggested solution for the time being.
Great suggestion @jmbolfing. I will send this along to the appropriate department.
Copyright All Rights Reserved © 2008-2023