Asset Prime | Customization of Asset Picker Filters
I’m exploring how to add additional metadata-based filters to the Content Advisor / Assets Prime picker used from AEM Sites.
The goal is to configure business filters such as Asset Type, Brand etc so that Sites authors can more easily find assets in the remote Assets Prime picker.
Based on the Customize Content Advisor documentation Customize Content Advisor | Adobe Experience Manager, I tested the filterSchema configuration with:
- type filters such as image/jpeg or video, image
- property=metadata.application.xcm:keywords.value
Both work successfully.
Now I want to add filters based on other OOTB and custom metadata. Since metadata for filters must be available in Searchable Properties (/adobe/repository?resource=searchableproperties), I’ve picked a few properties already available there, with search:indexed=true:
- repo:modifiedBy
- repo:createdBy
- repo:modifyDate
- repo:createDate
I injected these into filterSchema and selected these filters in the Assets Picker. However, applying any of these filters in the format metadata.application.<property> returns an HTTP 500 error. Instead, metadata.repository.<property> worked.
Eg format used:
{
header: "Created By",
groupKey: "CreatedByGroup",
fields:
[{
element: "text",
name: "property=metadata.repository.repo:createdBy=",
placeholder: "Created by"
}]
}
Similarly, custom metadata which are not present in the Searchable Properties (/adobe/repository?resource=searchableproperties) seem to work with metadata.embedded.<property>.
Does this mean the property is indexed but not visible in this endpoint?
These aren’t seen to be documented anywhere and I’m not sure if this is the recommended way to use these.
I want to know:
- What is the supported way to add additional metadata properties to Content Advisor filterSchema?
- How do we determine the correct filterSchema path for an OOTB or custom metadata property?
- What are the steps to make custom metadata available to Content Advisor and where to check it's searchability?
- Is there a way to identify what format of metadata properties are supported for filtering by the Assets Prime other than the two provided?
Environment: AEM as Cloud Service
Version: 2026.10.29023.20261017T134015Z