how to create custom Search assets filter in the AEM? | Adobe Higher Education
Skip to main content
K
karthick1356
Level 4
May 19, 2022
Beantwortet

how to create custom Search assets filter in the AEM?

  • May 19, 2022
  • 2 Antworten
  • 3480 Ansichten

I need to create custom asset filter and after creating custom filter it should visible along with OOB search assets filter.

User needs to see custom filter as well as OOB filter.

can any one explain with example that how to overlay this path /libs/settings/dam/search/facets/assets.

Dieses Thema wurde für Antworten geschlossen.
Beste Antwort von lukasz-m

Hi @karthick1356,

If I good understand under /conf you have only your custom fields, and you have removed all OOTB ones. If so this is correct behavior that you are seeing only your custom fields. Under /conf you should keep all the fileds OOTB and custom. OOTB fields will be automatically copied when you first time edit Assets Admin Search Rail  from GUI.

Below simple examples.

Scenario 1

I have added new field and also kept OOTB ones under /conf

Scenario 2

Only custom field is stored under /conf

Summarizing, if you need combination of OOTB and custom fields in filter section, you have to store them all under /conf. If there is any configuration under /conf it will be used instead /libs, and there will be no automatic merging of those two location in that case.

2 Antworten

lukasz-m
Community Advisor
lukasz-mCommunity Advisor
Community Advisor
May 19, 2022

Hi @karthick1356,

Please follow steps described under Adobe documentation - https://experienceleague.adobe.com/docs/experience-manager-65/assets/administer/search-facets.html?lang=en

In general, you have to:

  1. Navigate to Tools -> General -> Search Forms.
  2. Select Assets Admin Search Rail  from list and click edit.
  3. Set your changes and save.

Your customization will be stored under /conf/global/settings/dam/search/facets/assets/jcr:content/items - so this is part of content you can move to your git repository or include into crx package to propagate changes into other environments.

    K
    karthick1356Autor
    Level 4
    May 20, 2022

    Hi @lukasz-m,

    Yes, I have created custom filter that are stored under /conf/global/settings/dam/search/facets/assets/jcr:content/items . Now OOB filter from /libs/settings/dam/search/facets/assets and my custom from /conf/global/settings/dam/search/facets/assets/jcr:content/items  filter should merge and display for the user, but its not merging and display its displaying only custom filter one not OOB filter.

    I'm not sure what is the issue here?

      lukasz-m
      Community Advisor
      lukasz-mCommunity AdvisorAntwort
      Community Advisor
      May 20, 2022

      Hi @karthick1356,

      If I good understand under /conf you have only your custom fields, and you have removed all OOTB ones. If so this is correct behavior that you are seeing only your custom fields. Under /conf you should keep all the fileds OOTB and custom. OOTB fields will be automatically copied when you first time edit Assets Admin Search Rail  from GUI.

      Below simple examples.

      Scenario 1

      I have added new field and also kept OOTB ones under /conf

      Scenario 2

      Only custom field is stored under /conf

      Summarizing, if you need combination of OOTB and custom fields in filter section, you have to store them all under /conf. If there is any configuration under /conf it will be used instead /libs, and there will be no automatic merging of those two location in that case.

        manpreetk908
        manpreetk908
        Level 4
        May 20, 2022

        Hi @karthick1356,

         

        You can find the implementation of a custom asset filter along with the OOTB filters for your reference here -  https://experience-aem.blogspot.com/2020/02/aem-6530-assets-admin-search-rail-predicate-search-based-on-asset-id-jcruuid.html

         

        Hope it helps!

         

        Thanks,

        Manpreet

          Allgemeine NutzungsbedingungenAccessibility statement

          Loading footer...