Multiple selection not working when items are NOT adjacent in DYNAMIC FILTERS

I have created multiple lists of filter categories for users to narrow down their choice of options. Some filter categories allow users to select multiple options within the same list. If the options they select are not adjacent in the list, it will display NO MATCHES

example: if options are 1,2,3,4,5 - and user selects that they want 1 and 4 - DOES NOT WORK
example: if options are 1,2,3,4,5 - and user selects that they want 1 and 2 - it will work

Pictures for an example of: user selects 2 skills they are looking for. Three professionals MATCH these skill selections, but only ONE pops up, because the selections are adjacent in their column.



So when a user chooses highlights AND full blinding you only want to show stylists that have both 2?

Yes exactly. I want users to be able to check off multiple criteria, whether it’s 2, 3, 4 specialties etc. and the stylists who specialize in all of those things will appear.

Currently it only allows for multiple specialties if they are adjacent, or subsequent.

Hola,

I think this method can help you if you are going to use 4+ filters (btw… I tested your problem using my demo APP and everything worked ok) :

Saludos

1 Like

Hi @gvalero thank you so much for this information! While it is very similar to what I’m trying to create - I don’t think it is exactly the same. Let me see if I can explain…

The wide filter allows the results to only have SOME of the criteria in a filter section but not all…

For example: if you check off location Alcott rd AND downtown, it allows professionals to show up if they work at Alcot rd OR Downtown. I want mine to show the professionals that work at BOTH locations bc the user needs to go both locations.

This is currently how mine works EXCEPT if: let’s say Marie Rad said she worked at Alcott rd, downtown, AND beach locations but then a user only needed someone to who worked at Alcott and Beach… Glide misreads the criteria and says Marie Rad DOESN’T work at those locations bc in the database it reads Marie Rad works at “alcot rd,downtown,beach…” not the selection “alcot rd,beach”.

That’s what I was trying to show in my original photos. Hopefully that makes sense!! :pray:

Ah… I think now I follow you :upside_down_face:

In my demo, all users have an only one location, an only one title, etc and it isn’t covered.

Let me modify my database and play a while with your case to see if I can get something better for you.

Feliz dĂ­a!

@gvalero THANK YOU, THANK YOU

1 Like

Hola @Katelyn_Alberts

I keep trying to find out a simple and useful solution for you.

I tested 2 workarounds but I guess these are tricky for your case.

Your idea fails because you are using the includes condition in your filter and when your selected services (or hair types or whatever) aren’t consecutive the string/text to be found doesn’t exist. I have an idea using an array for it, it should work and make the solution simple.

I let you know when I have the idea working.

Feliz dĂ­a!

You are THE BEST. Thanks for keeping me updated and continuing to work on this!!!

Hola de nuevo,

here we go…

I’m going to use another version of my database to make some analogies with yours. Here you can see that I selected 3 different locations and the Filter showed 2 people with this criteria. Although you case might need 2 options, I show you a case with 3 options (up to 3 locations) to understand better the process.

This is the step by step to follow:

  1. Take data saved in your Service column (mine is called u_Location instead) by Choice component (multi selection) and create a new one based on it to have an array column.
    You must use Split Text type to get it.
    I called it u_Location[ ] but you can call your new column as u_Service[ ]

  1. Create 3 new columns using Single Value type in order to retrieve each value from u_Location[ ]. Keep in mind this column is an array and starts from 0 to 2 (3 items)

… This is how the 3rd column should look like.

  1. Ok… we almost finished :innocent:!

  2. Set your Inline List’s filters to work with 3 new columns created in step #2 using the includes condition. Your multiple selection should work fine from now on.

My Location column is equivalent to your My Specialty Service column

I hope it helps you @Katelyn_Alberts , let me know any problem if my explanation was not clear.

Feliz dĂ­a!

2 Likes

Oh this looks good!! I’m going to try this out tomorrow!!! Hopefully i can follow, but i am also still somewhat new so I may get lost and need help :innocent: i will let you know asap, thank you so much!

Here’s my attempt to do this to choose however many items you need from the choice component:

The idea is as below:

  • Have a unique table to store all locations.
  • Return a list of rowIDs that belongs to each location.
  • When you choose a filter item, return that list of rowIDs, so ultimately what we have is an array of rowID arrays.
  • I use JavaScript to return the rowIDs that appears in all child arrays (thus satisfying the AND condition).
2 Likes

Thank you! I will try this asap as well!

Hola Thind,

Smart idea, I was going to use something similar but I wanted to keep the solution easy based on Katelyn’s need and her knowledgement.

I didn’t want to confuse her with some JS code :innocent:

Chao, te cuidas!

1 Like

YOU ARE A GENIUS. It works perfectly and I have adjusted all my filter categories. I also love that I can put a limit on how many selections are being acknowledged in the filter without having to limit how many specialties someone can have aka: if a user selects more than 5 specialties it’ll only acknowledge the first [5] bc that’s all I allowed for, but the professionals can have more than 5 specialties in their profile.

THANK YOU, THANK YOU!!!

1 Like

Yeah, I agree with this, but I thought limiting the number of filters a user can use is not practical, so a more complex situation is proposed if she ever wants to come back in the future.

Yours is a great one.

1 Like

This topic was automatically closed 24 hours after the last reply. New replies are no longer allowed.