AEM Assets: Custom asset type filter shows no results due to MIME type configuration
✨ This content is AI generated and could be inaccurate. Generative AI Terms
This article explains why a custom ‘Asset type’ filter in Adobe Experience Manager Assets may not display results and provides steps to resolve the issue by updating the filter configuration.
Description description
Environment
- Adobe Experience Manager (AEM) Assets (all versions)
Symptoms
A custom filter for Asset type in the Assets view does not display any results for certain types (for example, Documents), even though assets of those types exist in the repository. The filter works for Images and Videos when configured with image/* and video/*. The filter for Documents is configured as document/* but returns no results. No error messages are shown in the UI.
Cause
The custom filter was configured with document/*, but AEM does not use a standard document/* MIME type. Document assets are stored with various application/... MIME types, so the filter did not match any assets. The built-in preset is mapped to the correct list of MIME types and should be used or replicated in custom filters.
Resolution resolution
Follow the steps below to resolve the issue.
-
Navigate to the filter settings for the custom ‘Asset type’ filter in Assets View.
-
Check the value used for the Documents filter.
-
If the filter uses
document/*, update it to a comma-separated list of actual document MIME types used in your environment, such as:-
application/pdf -
application/msword -
application/vnd.openxmlformats-officedocument.wordprocessingml.document -
application/vnd.ms-excel -
application/vnd.openxmlformats-officedocument.spreadsheetml.sheet -
application/vnd.ms-powerpoint -
application/vnd.openxmlformats-officedocument.presentationml.presentation
-
-
Alternatively, remove the custom Documents filter and re-add the built-in Documents preset, which is mapped to a list of known document MIME types.
-
Save the changes and reload the Assets View.
-
Test the filter to confirm that document assets are now displayed as expected.