After upgrading a staged environment from 6.2 to DXP, the tag function does not work properly

Please be aware that the page you are viewing has been machine translated from Japanese into English and may contain some translation errors. If you observe any issues with the translation, please contact us.

Issue

• There is a staging configured Portal 6.2 environment
• There is a tag filtering setting in the asset publisher
• After upgrading to DXP, when I run the publish process from staging to production, nothing appears in the asset publisher

Environment

• Portal 6.2,DXP 7.0,DXP 7.1,DXP 7.2

solution

• Starting with DXP 7.0, a uuid_ column has been added to the AssetTag table.
• Ifuuid_is different when staging publication, it is recognized as a different tag, so a new tag is generated with "duplicate" added after thetag.
• Content is not displayed in the asset publisher because it is outside the filtering criteria
• To fix this issue, you need to create a hotfix containingLPP-39439
• If necessary, create a ticket requesting hotfix creation

Additional Information

• The following operations are requiredThere is also no problem in uninstalling said Hotifx after the upgrade is completed.
  
  • Apply hotfixes to each environment
  • First upgrade the production database
  • In a staging environment, set up the following files
  Target file：
  

  STAGING_LR_HOME/tools/portal-tools-db-upgrade-client/portal-upgrade-ext.properties

  Additional content：
  

  jdbc.live.driverClassName=「本番側のdriverClassName」
  jdbc.live.url=「本番側データベースのURL」
  jdbc.live.username=「本番側データベースのユーザー名」
  jdbc.live.password=「本番側データベースのパスワード」

  *The contents to be set for each parameter are the values used in the database settings on the production side.
  
  
  • Upgrade staging side database
  • Verify that the uuid_ in the AssetTag table matches in staging/production