Unexpectedly high asset count in AEM Assets filter search
Filter searches for assets based on specific metadata return an unexpectedly high number of results in Adobe Experience Manager as a Cloud Service (AEMaaCS) – Assets. This occurs when AI Search stays enabled or when read access to the required Omnisearch and semantic search configuration paths isn’t available. To resolve the issue, update the Omnisearch configuration and grant the required read permissions.
Description description
Environment
- Product: Adobe Experience Manager as a Cloud Service (AEMaaCS) - Assets
- Scenario: Asset filter search with metadata criteria and AI Search enabled
Issue/Symptoms
- Filter searches for specific metadata values return far more assets than expected, such as 500+ results instead of a smaller, relevant set.
- The network request includes a
?{}?prefix before the search text. - Search results appear inconsistent between normal and incognito or private browser sessions.
- Affected accounts don’t see the same result set as admin accounts.
Resolution resolution
To resolve the issue, follow these steps:
- Navigate to Tools
>Assets>Assets Configurations>Assets Omnisearch Configuration. - In the Search section, select Keyword to disable AI Search for exact matching.
- Save the configuration changes to apply the updated search behavior.
- Grant
jcr:readpermission to everyone on the principal on/conf/global/settings/dam/assetsomnisearchand/content/dam/appdata/semanticsearch. - Log out of AEM and sign back in to refresh permissions.
- Run the same asset filter search again and confirm the results now align with expectations.
Notes:
- When AI Search is enabled, results are based on semantic relevance, not exact keyword matches.
- If users don’t have read access to required configuration paths, searches default to semantic (AI) behavior—even when Omnisearch is set to Keyword.
- A forthcoming product update will further improve identifier-based searches affected by this behavior.
3d58f420-19b5-47a0-a122-5c9dab55ec7f