Instead of using the query manager which is not the correct way to do this (not sure why you are doing it that way), reload the server connect from an action or flow, passing the new parameter to the route and this should do what you require automatically refreshing the data.
so your route is:
/availability/:building
then from a dynamic event (not sure how you are actually doing it but could be mouse click, form input onchange() or similar re-load the server action passing the new parameter (in your case i assume that is dynamic)
the data will automatically be refreshed with reference to the new parameter
1 Like
I make this solution and works. But if you want to create a unique url that redirect to specific results, you need to have de URL query string. This works only if you have a variable setup on the route panel for this page. If you dont have any variable the URL query string dont work. Thats why I think is a bug.
Of you want to hard code to a specific result such as building=edificio1then try something like
availability/edificio1
But dont have any logic that if you put any URL query string that is not declared goes to error 404. Is a problem with php server. On MAMP works perfect. Only works if you put a variable on the route even if is a dummy that you dont use it later. I dont know how to explain me better.
Because $_GET parameters are not compatoble with routing, Routes are intended as an alternative, they are not additive.
but why on MAMP works perfect.? Even on online server works fine?
Just because you can make it work does not make it correct. I just don’t understand your obsession with using parameters as this is totally unnecessary, the whole point of routing is NOT to use $_GET parameters.
Anyway, I have given my opinion, I don’t think I can contribute further.
1 Like
Thanks 
As you can see I report any bug that I find. I really want to contribute to improve wappler. Sometimes I dont get the technical issue behind. But it have been very emotional learning curve. I see a lot of your videos and learn a lot from there.
This is the last project I am working on and I think I am getting better I like a lot Wappler and feel the support of the community. Thanks to all.
https://beta.solanahuatulco.com/availability
Nice looking site.
To summarise:
Using the inbuilt wappler server, you have access to php via cli, you do not have an apache server running so routing is simulated with some php code
With MAMP, you have an apache server running so it can parse the $_GET parameters directly and allow you to mix technologies.
In my view this is more of a apache exploit than a intended behavior and as such can never rely on it not being depreciated.
There is always a routed alternative which is preferable.
