Search configurations for AEM Assets | Community
Skip to main content
raf-winterpacht
New Participant
May 28, 2025
Solved

Search configurations for AEM Assets

  • May 28, 2025
  • 2 replies
  • 497 views

I am looking for some recommendations on configuring Search for AEM Assets. I know that the search rail can be customized to a certain extent. Would it also support having a little more dynamic behavior, such as hiding a panel if a dropdown value is selected? This is for AEM as a Cloud Service.

Best answer by lukasz-m

Hi @raf-winterpacht,

This is not possible just using configuration abilities that can be found in Assets admin search rail. In general OOTB you can only add new fields an correlate it with asset metadata. There is no support for any interactions/dependencies between fields.

To achieve your goal, I am afraid you will need to do some development.

If you are using standard Assets view/search, you can try to create a clientlib where you will put your custom logic that will define dynamic behavior between fields.

In case you are using new Assets view, you will need to use App builder approach.

2 replies

Vishal_Anand
New Participant
June 9, 2025

You can always leverage smart collection option. 

1. Perform a Search:
  • Navigate to the Assets UI and use the search icon to enter your search criteria.
  • Apply filters to refine your search results. 
2. Save as Smart Collection:
  • Select "Save Smart Collection" from the toolbar. 
  • Provide a name for the collection and choose whether to make it public or private. 
3. Edit and Manage:
  • You can edit the Smart Collection's settings later to adjust filters, name, or accessibility. 
  • Edit Smart Collection options include saving the collection under a different name and selecting or clearing the Public checkbox, according to the Experience League. 
lukasz-m
lukasz-mAccepted solution
New Participant
June 1, 2025

Hi @raf-winterpacht,

This is not possible just using configuration abilities that can be found in Assets admin search rail. In general OOTB you can only add new fields an correlate it with asset metadata. There is no support for any interactions/dependencies between fields.

To achieve your goal, I am afraid you will need to do some development.

If you are using standard Assets view/search, you can try to create a clientlib where you will put your custom logic that will define dynamic behavior between fields.

In case you are using new Assets view, you will need to use App builder approach.