Adobe Experience Cloud
AEM Content Advisor filters fail when metadata uses the wrong namespace
Diagnose HTTP 500 from AEM Content Advisor metadata filters before changing the authoring experience.
November 9, 2026
An author can browse the remote asset picker until they select a new business filter. Then search returns HTTP 500. In a recent AEM Sites question, metadata.application.xcm:keywords.value worked, while placing repository properties such as repo:createdBy under metadata.application failed. The reporter got metadata.repository.repo:createdBy working. That is a useful clue, not a universal mapping rule.
Check the property path before the UI
Capture the exact filterSchema field, selected value, repository, response status and AEM version. First test a known working filter, then the failing field alone. This separates a search-property problem from a combination of filters. Adobe's Content Advisor properties document filterSchema; its shape alone does not establish that a field path exists in the searchable index.
Inspect the property's actual bucket in the search response and Searchable Properties for the same environment. Adobe's custom search filter guidance says custom filters must map to entries in the Searchable Property Index. An indexed property with the wrong namespace in the filter expression still points to the wrong place.
Make the fix reviewable by authors
Test the corrected path with one repository and a small set of known assets. Compare expected result counts and access rights, not just whether the HTTP error disappears. Then ask an author to find a real asset using the new filter. If the author cannot distinguish Brand from Asset Type, the technical fix has not solved the discovery problem.
Keep the mapping in configuration documentation so another team does not copy a working application path onto a repository field. Escalate persistent 500s with the request and property evidence rather than a screenshot alone.
Adovo’s view
Asset findability starts with a trustworthy vocabulary. A filter that fails only when people use it is worse than a missing filter because it trains authors to bypass metadata. Prove the property path, then prove the author can find the right asset.
