@srikanth7792 you have correctly mentioned the OOTB feature in your post, more info described in Adobe doc: https://experienceleague.adobe.com/docs/experience-manager-64/assets/administer/metadata-import-export.html?lang=en Can you please elaborate more on the specific custom requirement?

@chetan001 You first need to configure Brand Portal publish setup as described here: https://experienceleague.adobe.com/docs/experience-manager-cloud-service/assets/brand-portal/configure-aem-assets-with-brand-portal.html?lang=enBy default, the assets will only be published to the default publisher and not brand portal.Once done, you can simply do a quick publish and check the asset in Brand Portal.Hope this helps.

@harsingh91 I faced this issue once, as the file extension was causing confusion for AEM.There are multiple extensions available while saving the updated CSV file, make sure you check carefully and retry upload. If you still face any issues, refer to this help doc for header info: https://experienceleague.adobe.com/docs/experience-manager-64/assets/administer/metadata-import-export.html?lang=en Hope this helps.

you can simply paste the smart tag in AEM OOTB search bar and hit enter. You will see all the results containing that specific tag.Shortcut: / + Enter

I suggest raising a support ticket with Adobe Daycare team. They should be able to check the URL inconsistencies and provide a working sandbox.

hi @Adobe_CQ_Dispat It seems you don't have appropriate permissions to perform this operation.If you are an admin/or need to contact an admin, please assign the group experience-fragments-editors from user permissions page.You can find more info here: https://experienceleague.adobe.com/docs/experience-manager-65/assets/fragments/content-fragments-managing.html?lang=enAlso, user management in AEM: https://experienceleague.adobe.com/docs/experience-manager-64/administering/security/security.html?l...

Hi @highlighterpen Adobe provides ACS Common utilities for bulk asset operations, called MCP tools.You can try the renovator tool as described here: https://adobe-consulting-services.github.io/acs-aem-commons/features/mcp-tools/renovator/index.html

After a rigorous experimenting on this topic for 3 months or so, I was able to find the solution.Posting it for the community users.- disabled xmp write back workflow launcher- enabled out-of-the-box "Set last modified date" workflow launcher- created a translation integration config. Go to Tools - Cloud Service - Translation Cloud Services- In this config, make sure you uncheck the box for translating assets, and only enable it for tags and metadata (if desired). Also, set it to "Auto Execute T...

Never experienced the issue personally, but you might want to have a look at this article (non-Adobe): https://github.com/AdoptOpenJDK/openjdk-docker/issues/75

This error indicates that your XML has markup following the root element. In order to be well-formed , XML must have exactly one root element , and there can be no further markup following the single root element.One root element example (GOOD) The most common sources for this error are:Including stray or extra close tags (BAD): Intentionally having multiple root elements (BAD): Unintentionally having multiple root elements (BAD): Parsing different XML than you think (BAD):Log the XML immediately before providing to the parse that's failing in order to make sure that the XML that the parser is seeing is the same as the XML you think it's seeing. Common errors here include:The filename of the XML document being passed to the parser differs from what you believe it is.The buffer of the XML being dirty. Make sure it's been cleared prior to adding your XML.An earlier program from a prior stage in your pipeline changing the XML prior to the parsing that's yielding this error message.

What happens when you select the PDF> click More Info? Does that open a viewer for you to navigate through pages?If not, you can integrate Dynamic Media with AEM to get viewers functionality enabled. https://experienceleague.adobe.com/docs/experience-manager-65/assets/dynamic/administering-dynamic-media.html?lang=en https://experienceleague.adobe.com/docs/experience-manager-65/assets/dynamic/managing-viewer-presets.html?lang=en

Append Mode is used to append the new metadata with the existing metadata in fields that contain multiple values. If you do not select this option, the new metadata replaces the existing metadata in the fields.You can find more info here: https://experienceleague.adobe.com/docs/experience-manager-64/assets/managing/managing-multiple-asse...

Append Mode is used to append the new metadata with the existing metadata in fields that contain multiple values. If you do not select this option, the new metadata replaces the existing metadata in the fields.You can find more info here: https://experienceleague.adobe.com/docs/experience-manager-64/assets/managing/managing-multiple-assets.html?lang=en