Then wherever in your workflow you’re adding the values to your variable (in my case it’s a multiselect field) use the Join formula to turn the array into a comma seperated list. This is also how it will appear in your URL ( url.com?variable=value1,value2 )
Now over in your data source, where you bind the input to your api call, you’ll be wanting to turn that comma seperated string back into an array, so that you can feed the array to your API call (in my case in xano, I have an input>text>list
I have never used query types actually. Can you expalain why there usefull in this case? Could you just create an array variable and then you wouldn’t need to do the join or the split.
Soo in my case I have a page with listings, and filters on the left. I want the URL to change when people click on the filters, so that eg. if they share a link of a filtered page, or bookmark it or whatever, that url matches the filters. This way the ‘back’ button on your browser also behaves in a way that you can cycles back to previous filtered views. It’s pretty much common practice for those kind of pages
This only works if you make the variable that stores your filter a query type