Tealium / integration-sitecore

Other
2 stars 1 forks source link

Tealium Tag Management module Issue during Sitecore 9.1 Initial release upgrade from Sitecore 8.1.2 #3

Open SharathMP opened 5 years ago

SharathMP commented 5 years ago

Hi Team,

Current data: Currently we are running on Sitecore 8.1.2 with Tealium Sitecore Tag Management module with Version 1.0.0.0. Problem Statement: We are trying to upgrade to Sitecore 9.1 Initial release, but we are getting error with the current version of Tealium Sitecore Tag Management module. Can you kindly check if the current version of the module does support Sitecore 9.1.0 or do we need to upgrade the Tealium TagManagement module as well? If yes kindly suggest the version of the Tealium TagManagement module?

Supporting documents:

  1. Snapshot of current version of Tealium Tag Management module
  2. Sample Error snapshot during upgrade

Current Version of the Tealium TagManagement module: 1.0.0.0

Tealium

Sample upgrade Error Message related to Tealium TagManagement:

612 Warning filesystem Custom code should be recompiled Type Tealium.Sitecore.TagManagement.CustomFields.SiteSelectorDroplist from assembly Tealium.Sitecore.TagManagement inherited from the type that has got breaking changes. Type Sitecore.Web.UI.WebControl defined in assmebly Sitecore.Kernel has got breaking changes. Custom type Tealium.Sitecore.TagManagement.CustomFields.SiteSelectorDroplist defined in assembly Tealium.Sitecore.TagManagement derives from the changed type and might be affected. Custom assemblies need review Force \report.bc_addedbreakingchangesfiles_CF9D3A5917B1443FA9027864FF880EB8 BreakingChangeUsageFoundErrorMessage DerivedFromModifiedTypeErrorMessage [] Regards, Sharath
SharathMP commented 5 years ago

Hi Team,

Please help with the above query.

Regards, Sharath

tygavin commented 5 years ago

There are versions to download here: https://github.com/Tealium/integration-sitecore/tree/master/releases

Documentation: https://github.com/Tealium/integration-sitecore/tree/master/documentation

Let me know if the latest 1.0.2.0 release resolves the issue