DocumentationExperience Cloud KCS

AEM as a Cloud Service: Make custom Content Fragment properties searchable in New Assets UI

Last update: July 27, 2026

This article explains the steps required to make custom Content Fragment properties searchable in the New Assets UI in Adobe Experience Manager as a Cloud Service.

Description description

Environment

Adobe Experience Manager as a Cloud Service (AEMaaCS) (all versions)

Symptoms

  • Custom properties added to Content Fragments aren’t searchable in the New Assets UI (Assets view), even though some fields are searchable in the classic DAM Assets Admin UI.
  • Custom Content Fragment fields are indexed in a custom Lucene index and are searchable via the classic Assets Admin UI.
  • The same fields don’t appear as available search fields or filters in the New Assets UI.
  • Attempts to adjust index configuration (such as adding fields, changing property types, increasing boost, or reindexing) don’t resolve the issue for the New Assets UI.
  • No specific error messages are shown, but the expected search/filter functionality is missing for custom Content Fragment properties.

Cause

The New Assets UI uses a different search mechanism that requires custom properties to be exposed through the Searchable Property Index in addition to being included in the Lucene index. Without this configuration, custom Content Fragment properties won’t be searchable in the New Assets UI.

Resolution resolution

Follow the steps below to resolve the issue:

  1. Review the search architecture: The classic Assets Admin UI uses QueryBuilder directly against Oak/Lucene indexes, while the New Assets UI relies on the AEM Repository API (R-API) and the Searchable Property Index. Only properties exposed with search:indexed: true are available for search and filtering.
  2. Verify Lucene index configuration: Ensure custom Content Fragment properties are included in your custom Lucene index overlay. If properties are of type Long, either change them to String type or explicitly include Long properties in your custom index overlay.
  3. Expose properties in the Searchable Property Index: Add the required custom properties to the Searchable Property Index configuration so they appear as search fields and filters in the New Assets UI. Properties must be under jcr:content/metadata/... to be usable in Assets view filters. Properties under jcr:content/data/... aren’t supported for this purpose.
  4. Reindex after configuration changes: After updating index configurations and the Searchable Property Index, trigger a reindex to ensure changes take effect.
  5. Validate in the New Assets UI: Confirm that the custom properties now appear as available search fields and filters in the New Assets UI. Test search functionality to ensure the properties are searchable as expected.
recommendation-more-help
experience-cloud-kcs-help-kbarticles