Cannot Save an Advanced Search as a Collection within Recommendations | Community
Skip to main content
B
BenMu6
Level 3
May 30, 2023
Solved

Cannot Save an Advanced Search as a Collection within Recommendations

  • May 30, 2023
  • 1 reply
  • 1628 views

Hello,

Wondering what might cause the 'Save as' option to gray out/not be available within the Catalog Search > Advanced Search window? I've added a number of rules/filters to the data set and I'm returning a few hundred entities, however, when attempting to save the search as a collection or exclusion it's not working. Any known reasons for this? Anything to look at to troubleshoot?

    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 JacobTo1

    Hi @benmu6 
    Funny I've experienced the same frustrations myself and have found 2 workarounds for the "value exists" but you could probably play around with them to achieve the inverse logic..

    1. If there is a common substring in all values of that attribute you can just use "contains substring" (e.g. all images are hosted on a common domain or path).
    2. If this is not possible I've used the following and it seems to give me the same result as "value exits"
    "is greater than or equal to" and the value 0

     

    1 reply

    J
    Adobe Employee
    jmosbaugAdobe Employee
    Adobe Employee
    June 7, 2023

    Hello ben

    This is most likely due to selecting a filter in the Advanced search that does not exist in collection creation. 

    I created an advanced search where name contained the letter "a" and thumbnailUrl contained string "recs". At that point I could still save as a collection. 

     

    I then added a filter for message value is present and the collection save greyed out. 

    Verify that the search parameters you are using in advanced, exist in the Collections UI. 

     

      B
      BenMu6Author
      Level 3
      June 8, 2023

      Thanks! Yeah, I think that's exactly it. My question would then be, why are certain filters available within the Advanced Search feature but not within a collections rules set?

      Example being, I'm seeing operators available within the Advanced Search that are really useful like the "value is present" or "value is not present", however, these do not appear within the rules under the collections. Do we know why?

       

       

       

        J
        JacobTo1Accepted solution
        Level 4
        June 15, 2023

        Hi @benmu6 
        Funny I've experienced the same frustrations myself and have found 2 workarounds for the "value exists" but you could probably play around with them to achieve the inverse logic..

        1. If there is a common substring in all values of that attribute you can just use "contains substring" (e.g. all images are hosted on a common domain or path).
        2. If this is not possible I've used the following and it seems to give me the same result as "value exits"
        "is greater than or equal to" and the value 0

         

          Terms & ConditionsAccessibility statement

          Loading footer...