12-01-2014 04:55 PM - last edited on 12-17-2015 01:36 PM by kathleen_jo
Honestly, if the extension has values that are specific to a profile, it's best to create a unique instance of the extension specifically for that profile. This can be time consuming with many profiles, I will admit. If you add an extension in a library, it's assumed that you don't want to change anything about that extension for your linked profiles, unless you want to change it for all of them. Currently you can't overwrite an inherited extension locally. Your suggestion from your other question (https://community.tealiumiq.com/t5/Developers/How-to-correctly-setup-Library-Architecture/m-p/6188 about allowing a user to modify an extension inherited from a library make sense to me. We do plan on revisiting profile libraries and inheritance in the future (much as we do for all of our functionality), but I can't give you any timeline on this. One thing I'd recommend is that you contact your Tealium account manager about these suggestions; direct customer feedback through our account managers is a great way to get the ball rolling on feature enhancements. Your method of duplicating a disabled library-inherited extension does work, as you've no doubt noticed. From what you've described, this does seem to be the most effective solution. But I understand that this too is cumbersome. Moreover, one thing you may run into is that when you need to change the extension in the library, you'll have to go back into the profile (which inherits that library) to re-duplicate the extension. The duplicate of the original library-inherited extension doesn't update dynamically like that. So, while you do bring in the inherited base you plan to modify in the profile, you still have that manual effort of duplication. Keep the good ideas coming though. We do appreciate feedback.