Ability to propagate tag updates on custom fields referencing them | Community
Skip to main content
mikeetiuPH
mikeetiuPH
Level 4
January 17, 2023
Investigating

Ability to propagate tag updates on custom fields referencing them

  • January 17, 2023
  • 3 replies
  • 679 views
Request for Feature Enhancement (RFE) Summary: Ability to propagate tag updates on custom fields referencing them
Use-case: We have custom fields that are referencing tags. Whenever there are updates on the tag hierarchy like updates and deletions, we would need to do a lot of page re-tagging and updating since the updates are not cascading automatically.
Current/Experienced Behavior: Changes on the tag hierarchy does not automatically reflect on custom tag fields
Improved/Expected Behavior: Changes on the taxonomy should automatically reflect on the pages using them
Environment Details (AEM version/service pack, any other specifics if applicable): AEMaCS
Customer-name/Organization name: N/A
Screenshot (if applicable):  
Code package (if applicable):  

3 replies

kautuk_sahni
Community Manager
kautuk_sahniCommunity Manager
Community Manager
January 25, 2023

@mikeetiuph 

Thanks for proposing this idea

This has been reported to the engineering under the internal reference CQ-4351628. The product team will triage this request to verify feasibility based on the prioritization model. This post will be updated according to the Jira request status.

Kautuk Sahni
E
Adobe Employee
ehahn061Adobe Employee
Adobe Employee
January 27, 2023

@mikeetiuph This is great feedback and we are looking into this. Could you provide a bit more detail around the use case? I would expect to see the tag values update, but I'm curious where you are using them.

 

Are these custom fields on page properties or in components in the UI? Any additional detail you could provide would be great. 

mikeetiuPH
mikeetiuPHAuthor
Level 4
January 28, 2023

Hi @ehahn061 - basically, we didn't use the out-of-the-box tags field in on the page properties because some of our customers want to have "tag" fields that are more specific for reporting purposes. 

So in the properties, we have fields like "Content Type" or "Targetted Audience" which are populated by selecting tags. Does this make sense? 

Terms & ConditionsAccessibility statement

Loading footer...