Highlighted

Duplicate data variables when linking a library back into the profile from which it was created

Bronze Contributor
Bronze Contributor

I’m looking for some advice on the best way to link a library back into the profile it was created from.

 

First, some background: We started with profile A that had all the data variables, load rules, tags, and extensions we needed for the version of our site that we serve to country A. Then we built out sites for countries B and C, and knew that it would share tealium data and logic with profile A. So, we created a library from profile A (stripping out all the stuff that was specific to country A), and then linked that library into profiles B and C.

 

Now the issue: Once profiles B and C stabilize we want to link the library back to profile A, which of course has tons of duplicates with the library. Having duplicate load rules, tags, and extensions is okay, since we can simply remap everything and delete the old versions. However there is a problem when it comes to the data layer: It seems that the only library variables imported are the ones that do not already exist in profile A. Any variables that exist in both profile A and the library remain in profile A. I would expect these to be converted to library variables.

 

What is the best way around this situation? The only option I can think of is to create a brand new profile (A-prime), link the library, copy all the profile-A-specific stuff over to it manually, then delete profile A. I really don’t want to have to do that...

 

Thanks for your help.

2 REPLIES 2
Highlighted

Duplicate data variables when linking a library back into the profile from which it was created

Tealium Employee

Hi @zak_linder

 

When you say "It seems that the only library variables imported are the ones that do not already exist in profile A", that is correct and by design. The profile data sources trump those of the library since the library is inherited and typically only a subset of configs.

 

I would say you can take the same approach with the data layer as you did with the duplicate load rules, tags, and extensions where you can simply delete the profile variables and remap the library data variables. This can get a bit tricky since the UI will tell you that mappings or configs are missing, so you may need to go though and pre-select a dummy attribute.

 

Either way, it will take some manual effort to do this. I understand it's not a highly desirable option and I apologize for that.

 

Cheers,

-Dan

Highlighted

Duplicate data variables when linking a library back into the profile from which it was created

Bronze Contributor
Bronze Contributor
Thanks for the response, Dan!

Just to be clear, you’re suggesting that I delete all the variables in profile A that are in the library, and then link the library?