AEM as a Cloud Service: Assigning custom metadata forms only to Content Fragments
✨ This content is AI generated and could be inaccurate. Generative AI Terms
This article describes the current product behavior and available workarounds when assigning custom metadata forms only to Content Fragments, and not to page-type assets, within the same folder in Adobe Experience Manager as a Cloud Service.
Description description
Environment
- Adobe Experience Manager (AEM) as a Cloud Service (all versions)
Symptoms
When enabling custom metadata forms (for example, with fields such as anchorId and Visual spacing) for Content Fragments in the Assets View, there is a requirement to apply the custom metadata form only to Content Fragments and not to page-type assets within the same folder. This is typically done using a “CMS as code” approach for consistent configuration across multiple environments and regions.
When a metadata form is assigned to a folder in Assets View, it is applied to all assets in that folder and its subfolders, regardless of asset type (Content Fragment, image, document, or page). There is no error message, but the product does not support type-based assignment of metadata forms within the same folder.
Cause
The current product design in AEM as a Cloud Service only supports folder-based (not type-based) assignment of metadata forms in Assets View. Restricting a metadata form to only Content Fragments within a folder that also contains other asset types is not supported.
Resolution resolution
Follow the steps below to resolve the issue.
- Store Content Fragments and page-type assets in different DAM folder hierarchies.
- Assign the Content Fragment-specific metadata form only to the folders containing Content Fragments.
- Assign the default or a different metadata form to folders containing page-type assets.
- If separating folders is not possible, configure field-level visibility rules using cascading metadata so that Content Fragment-specific fields are only visible when the asset is a Content Fragment. Hide fields that are not relevant for page-type assets.
- Ensure all metadata form definitions and folder assignments are included in your deployment packages to maintain consistent configuration across all environments and regions.