Custom metadata schema not visible in Experience Manager Assets with 404 Error
This article explains how to resolve an issue where a custom metadata schema is not visible in Experience Manager Assets, resulting in a 404 Repository Not Found error.
Description description
Environment
Adobe Experience Manager (AEM) as a Cloud Service
Issue/Symptoms
A user with appropriate group permissions can view a custom metadata schema (for example, “Craft Metadata Schema”) in the classic AEM Assets (Admin view), but cannot see the same schema in Experience Manager Assets (Assets View in experience.adobe.com). Only the Basic and Advanced metadata tabs are visible in Experience Manager Assets. Attempts to access the custom schema or its forms result in a 404 - Repository Not Founderror.
- The custom schema is configured and applied to the relevant folder in Admin view.
- In Experience Manager Assets, the custom schema is not displayed.
- Network logs and direct access to metadata forms return a 404 error.
- The same user permissions work correctly in classic Assets but not in Experience Manager Assets.
Cause
Experience Manager Assets and classic AEM Assets use separate metadata configuration systems. The 404 error occurs because the custom schema is not present as a metadata form in Experience Manager Assets, even if it exists in Admin view.
Resolution resolution
To fix the issue, follow these steps:
-
Understand Metadata Schema Differences
- Classic AEM Assets (Admin view) uses metadata schemas stored under
/conf/global/settings/dam/adminui-extension/metadataschema. - Experience Manager Assets (Assets View) uses metadata forms stored under
/content/dam/appdata/metadataforms, managed via Settings>Metadata Forms in the Assets View UI.
- Classic AEM Assets (Admin view) uses metadata schemas stored under
-
Confirm that the custom schema (for example, “Craft”) exists under
/conf/global/settings/dam/adminui-extension/metadataschemaand is applied to the relevant folder. -
Create or Import Metadata Form in Experience Manager Assets
- In Experience Manager Assets, navigate to Settings
>Metadata Forms. - Create a new metadata form that exposes the same fields as the custom schema, and assign it to the same folder(s).
- Alternatively, if available, use the Import Metadata Forms from Admin View to Assets View feature to bring the Admin schema into Assets View and associate it with the folder.
- See Import metadata form from Admin View to Assets View.
- In Experience Manager Assets, navigate to Settings
-
Log in as a user with the relevant permissions and verify that the custom metadata fields are now visible in Experience Manager Assets.