Content fragments not visible in DM Open API asset selector on authoring tier
In Adobe Experience Manager as a Cloud Service (AEMaaCS), Content Fragments stored under a DAM path such as/content/dam/... do not appear in the Dynamic Media Open API Asset Selector when connected to the authoring tier, while image assets in the same location remain visible and selectable. To resolve the issue, use supported asset types or alternate interfaces.
Description description
Environment
Adobe Experience Manager (AEM) as a Cloud Service (all versions)
Issue/Symptoms
- Content Fragments stored under a DAM path (for example,
/content/dam/...) do not appear in the Dynamic Media Open API Asset Selector when connected to the authoring tier. - Image assets in the same DAM folder are visible and selectable in the Asset Selector.
- No error messages are displayed; the Content Fragments do not appear as selectable assets. Example DAM path:
/content/dam/some-folder.
Root Cause
The Dynamic Media Open API Asset Selector is designed to include only binary assets for Dynamic Media delivery and excludes Content Fragments by design.
Resolution resolution
To resolve the issue, follow the steps below:
- Review the requirements for asset selection in the Dynamic Media Open API Asset Selector and confirm supported asset types.
- Understand that the selector is implemented on top of the Dynamic Media delivery repository and R-API.
- Note that this implementation focuses on binary digital assets such as images, videos, and supported documents.
- Recognize that the selector filters out Content Fragments by design and does not include them in the selection interface.
- Use alternative methods or supported interfaces when selecting or referencing Content Fragments within Adobe Experience Manager.
experience-cloud-kcs-help-kbarticles