Adobe Experience Manager: custom metadata schema not applied

Last update: 2022-11-30


This article provides a solution for the issue where you cannot change the default metadata schema.

  • Adobe Experience Manager

Steps to reproduce:

  1. Go to Tools, Assets, then Metadata Schemas, and copy the default Metadata Schema in the MetaData Schema Form Editor, and then make a change to the copy.
  2. Click Assign to folder(s), for example, the product folder.
  3. Although you see the new metadata schema in CRXDE Lite you cannot see the changes on the front end, in the MetaData Schema Form Editor.


Ensure you do not have the metadata schema in /dam/adminui-extension/metadataschema node in the project folder /conf/project ID. The project folder is not checked for custom metadata schema.

If you do, remove the node from that path. New schemas should be created in conf/global/dam/adminui-extension/metadataschema, the default for metadata schema. For more information, refer to the Metadata schemas, in the AEM as a Cloud Service user guide in Adobe Experience League.

On this page