Need help with getting files/folders selection in Asset Admin Search Rail back | Community
Skip to main content
N
ndlholm1
Level 3
October 6, 2023
Solved

Need help with getting files/folders selection in Asset Admin Search Rail back

  • October 6, 2023
  • 2 replies
  • 2069 views

Hello -- I need assistance with getting the files/folders/files & folders selection option back in our AEMaaCS Production environment. I'm not sure how to add the needed properties under "Show" in our Assets Admin Search Rail in Production. I was able to do this in Dev in CRXDE, but we don't have access to CRXDE in Production.

 

Any assistance is appreciated.

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by Adilos-Cantuerk

From the screenshots (what is brettingprod 🙂 i am not sure if this might be it,
shouldn't there be a path browser predicate which in turn would be above your show predicate?

Like this:

As is - how do you change the behavior on your production enviroment to be like in your development enviroment:
Usualy, you would have the changes made within the master branch and push it via the deployment pipeline.
But in case, you just want to try out, if this will do the changes you want it to do, you can try the following.
Go to your CRX package manager, create a new package, for /conf/global/settings/dam/search/facets - then download this package- upload and install it on your production enviroment to have the settings instantly. 

Edit: As written in addition: You need to put this change also in your master branch within the git, otherwise this will not be a permanent change. Your next deployment will overwrite the settings with whatever your settings are in your git - master branch.

2 replies

krati_garg
Adobe Employee
krati_gargAdobe Employee
Adobe Employee
October 9, 2023

@ndlholm1 There are three queries here:

 

1. Show is a OOTB search predicate that does not have any properties under it. If you have customized it and added any specific properties that need to be checked in as code into your GIT Repo and added required entry in filter.xml, so the build would add your custom changes to the new environment you are deploying to.

2. On my CS sandbox, the option for files list me out all the three options as OOTB drop down. Have you done some customizations into it? You might need to check error logs at both browser and backend for any issues with customizations.

3. Yes we dont have access to CRXDE in AEMaaCS, and hence we need to check in all out customizations in the code, to make it available on Production.

    Adilos-Cantuerk
    Community Advisor
    Adilos-CantuerkCommunity AdvisorAccepted solution
    Community Advisor
    October 9, 2023

    From the screenshots (what is brettingprod 🙂 i am not sure if this might be it,
    shouldn't there be a path browser predicate which in turn would be above your show predicate?

    Like this:

    As is - how do you change the behavior on your production enviroment to be like in your development enviroment:
    Usualy, you would have the changes made within the master branch and push it via the deployment pipeline.
    But in case, you just want to try out, if this will do the changes you want it to do, you can try the following.
    Go to your CRX package manager, create a new package, for /conf/global/settings/dam/search/facets - then download this package- upload and install it on your production enviroment to have the settings instantly. 

    Edit: As written in addition: You need to put this change also in your master branch within the git, otherwise this will not be a permanent change. Your next deployment will overwrite the settings with whatever your settings are in your git - master branch.

      N
      ndlholm1Author
      Level 3
      October 9, 2023

      Thank you so much, @adilos-cantuerk! This worked!

        Adilos-Cantuerk
        Community Advisor
        Adilos-CantuerkCommunity Advisor
        Community Advisor
        October 9, 2023

        @ndlholm1 Your welcome! I am glad i could help.
        But don't ignore what @krati_garg  wrote.
        You will still have to implement this code into your master branch in the git. 
        Otherwise your next deployment will set this back to the state your master branch has it.

          Terms & ConditionsAccessibility statement

          Loading footer...