Documentation

Custom asset metadata properties in subnodes of the metadata node do not appear in Content Hub metadata configuration UI

Last update: Fri Mar 06 2026 00:00:00 GMT+0000 (Coordinated Universal Time)

In AEMaaCS, when configuring Asset Details in Content Hub, only metadata properties stored in the “metadata” node are available for selection. Properties saved within subnodes of the ‘metadata’ node (such as under a custom path) do not appear in the configuration dropdown and cannot be referenced through the UI. To fix this, flatten your custom metadata properties into the ‘metadata’ node.

Description description

Environment

  • Product: Adobe Experience Manager as a Cloud Service(AEMaaCS) – Assets
  • Feature: Content Hub
  • Configuration: Custom asset metadata stored under subnodes of the metadata node

Issue/Symptoms

  • Custom asset metadata properties stored in subnodes of the ‘metadata’ node, such as /metadata/mh/brand, do not appear in Content Hub’s metadata dropdowns.
  • Only properties in the metadata node are available for selection.

Resolution resolution

To resolve this issue, follow these steps:

  1. Move custom asset metadata properties from subnodes to the metadata node directly.
  2. Use a proper namespace prefix for these properties to avoid naming collisions, for example mh:brand or xdm:brand instead of brand.
  3. Update any code, scripts, or integrations that reference the old nested property paths so they use the new direct property names.
  4. Validate that the migrated custom metadata properties appear as selectable options in Content Hub metadata dropdowns.
  5. Verify that the migrated custom metadata properties appear as selectable options in Content Hub’s metadata configuration dropdowns and are editable.
  6. After confirming the migration is successful, remove the older nested subnode structure to keep the metadata node clean.

Notes:

  • Content Hub does not support referencing nested or custom JCR paths through UI configuration alone.
  • This limitation requires backend changes to surface such metadata.
  • Flattening custom metadata properties and applying proper namespace prefixes provides the most compatible approach for Content Hub and related experiences.
recommendation-more-help
3d58f420-19b5-47a0-a122-5c9dab55ec7f