02-06-2017 08:21 AM
We have two libraries mapped to our publishing profiles. When we publish, we get to the profile, change the profile mappings from Dev Library to Prod Library, and then Publish. However, oftentimes when we switch the profile mappings, we end up with a situation where tealium IQ thinks that every data layer object, load rule, tag, and extension was updated - which seriously corrupts our log of what actual changes were made.
This is the case even when there is not difference between our dev and Prod version of the mapped libraries.
What's up? and can this get fixed?
02-06-2017 09:27 AM - last edited on 02-06-2017 09:44 AM by kathleen_jo
It sounds like you are switching libraries between dev and prod?
If so, anything included in those libraries will be marked as "changed" each time you switch.
Anything not include in the libraries will not be marked as changed.
Does this match what you are experiencing?
02-06-2017 11:32 AM - last edited on 02-07-2017 08:28 AM by kathleen_jo
Yes, @steve_lake, it matches. It's making it very difficult to idnetify the actual changes that were made for the production release however.
If my library dev, qa, and prod versions are all identical, and i switch my local profile to use prod instead of qa, i would expect that there would show "0" changes logically...?