Error while importing a metadata schema form in Asset View
When you try to import a custom metadata schema form into Asset View in AEMaaCS, the process fails if the form includes unsupported field types. These include advanced dropdowns or legacy components like metadataselect. Asset View doesn’t support these fields, so the import fails. To fix this, remove unsupported fields and use only supported field types before reimporting the schema.
Description description
Environment
- Product: Adobe Experience Manager as a Cloud Service - Assets (AEMaaCS - Assets)
- Environment: Production
Issue/Symptoms
- Importing a custom metadata schema form (
abc-metadata-schema``) into Asset View fails. - The schema includes unsupported field types such as advanced dropdowns or legacy components like
metadataselect. - These fields are incompatible with Asset View’s import functionality.
Resolution resolution
Asset View supports only a limited set of field types for metadata schema forms. Unsupported components, such as advanced dropdowns or dynamic fields built using metadataselect, will cause the import to fail.
Follow these steps to resolve the issue:
-
Review the metadata schema form and identify any unsupported fields. Examples include:
- Advanced dropdowns
- Dynamic multi-selects backed by scripts, JSON, or external sources
- Legacy components like
metadataselect
-
Remove unsupported fields from the metadata schema.
-
Ensure that only supported field types remain in the schema. Supported field types include:
- Text Field
- Dropdown (static options)
- Date Field
- Tag-based pickers
-
Reimport the updated metadata schema into Asset View.
Note: Asset View doesn’t support dynamic dropdowns or advanced/multi-select fields. Only static and tag-based pickers are supported.
Related Reading
Import metadata forms from Admin View to Assets View in the AEMaaCS User Guide