cq:name & cq:parentPath is not created in jcr:content after uplaoded the assets in dam | Community
Skip to main content
U
user65294
New Participant
February 1, 2024

cq:name & cq:parentPath is not created in jcr:content after uplaoded the assets in dam

  • February 1, 2024
  • 2 replies
  • 1191 views

Hi all, 

 

We're facing the issue cq:name & cq:parentPath is not created when we imported the assets in aem. Earlier its was working as expected. Currently we're using AEM on-prem version 6.5.18. Please suggest if anyone faced the same issue. 

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

2 replies

kautuk_sahni
kautuk_sahni
Employee
February 16, 2024

@user65294 Did you find the suggestions from users helpful? Please let us know if more information is required. Otherwise, please mark the answer as correct for posterity. If you have found out solution yourself, please share it with the community.

Kautuk Sahni
Saravanan_Dharmaraj
Saravanan_Dharmaraj
New Participant
February 2, 2024

@user65294 https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/cq-name-not-populated-for-aem-assets/td-p/599095

have you got chance to look at this? 

    U
    user65294Author
    New Participant
    February 5, 2024

    Hi Saravana, 

     

    yes, I looked into it. Dam metadata writeback WF is working but its not extracting the properties of cq:name & cq:parentpath.

      Terms & ConditionsAccessibility statement

      Loading footer...