DocumentationExperience Cloud KCS

Custom metadata not appearing in AEM Assets search filters

Last update: June 27, 2026

Custom metadata fields can appear on asset properties but not in AEM Assets View or Assets Essentials search filters. This issue occurs when the metadata property is not configured as a searchable property in the DAM asset index. Add the property to the DAM index, deploy the updated configuration, and verify that the property appears in the searchable properties list and search filters.

Description description

Environment

  • Adobe Experience Manager as a Cloud Service
  • AEM Managed Services
  • AEM Assets Essentials

Issue/Symptoms

  • Metadata fields appear in asset properties but not in search filters.
  • Search configuration does not list the metadata property.
  • Searchable properties output does not include the metadata field.
  • No error messages appear in the interface.
  • Newly added fields take time to appear after changes.

Cause

AEM Assets search filters display only metadata properties indexed as searchable properties in the DAM asset index. If the metadata field is not defined in the index configuration, it does not appear in search filters. Naming conflicts and namespace issues can also prevent the property from being indexed correctly.

How to confirm

  • Open the searchable properties endpoint
  • Verify whether the metadata property appears in the response.
  • Check that the property is marked as indexed.
  • Confirm the property exists in the DAM asset index.

Resolution resolution

Follow these steps to resolve the issue

  1. Verify that the property appears in the Searchable Property Index by navigating to /adobe/repository?resource=searchableproperties.
  2. Navigate to /oak:index and locate the latest damAssetLucene-XX index. Verify that the active index is the latest version.
  3. Create or update a custom overlay of the index in the project codebase.
  4. Add the required metadata property under the appropriate asset index rules.
  5. Enable indexing for the property by setting it to searchable.
  6. Trigger reindexing in the index configuration.
  7. Deploy the updated index through the deployment pipeline.
  8. Verify that the property appears in the searchable properties output. If the property appears with search:indexed=true but is not visible in Assets View, wait up to 6-15 hours for a full synchronization.
  9. Add the property to the search filter configuration in the Assets interface.
recommendation-more-help
experience-cloud-kcs-help-kbarticles