Struggling with URL Parameters

I’ve got a collection of products from Xano that I’m building out some user filters for. Ideally, I would like the URL to update with the appropriate query parameters so that they can share that URL (or bookmark it) and it will pull up the exact results they want.

The trouble I’m having is I’m able to update the query variables and get the correct results, but:

  1. When I change my dropdown filter, the URL doesn’t update with the parameter (even though the data reloads correctly)

  2. When I click the “Reset Filters” button, I can’t figure out how to get the dropdown to display the default “Biggest Price Drops” value.

Here is the workflow that fires when a user selects how they want the products sorted:

As you can see in the collection, the correct variables are placed (hence why my results are accurate, despite no parameters being added in the URL when I change values):

And here is the workflow that fires when the reset button is hit, it just resets all of the variables back to their default state:
image

And here are (some) of the settings for the dropdown:

Any idea as to what I am missing here?

2 Likes

Hi @brandon :wave:

It looks like you are updating Text variables. If you want to add query strings at the end of a URL, you’ll want to use Query variables instead:

Let me know if that helps! If not, I’ll have missed something and will take another look :slight_smile:

Thanks for your reply! I double checked and everything (as far as I can see) is listed as a Query type. As you can see in the /URL Filters folder, they all are queries:

As an update to @Joyce’s post, I can see now why you said they were text variables and not query variables. I noticed in the second screenshot on my original post the variables appear to be text (with the ‘abc’ icon). I just noticed that while working inside WeWeb just now.

Yet, when I go to the actual Variables section, it does show me they are set as a Query type. Is this by chance a bug?

Hi @brandon :wave:

Apologies for the late reply on this. Did you end up reporting a bug?