Hi Dojo,
after updating our DMS to 10.4.0 recently, we‘ve observed that some tables in one of our low-code apps were not showing any more data. After some investigation on the query that was populating the table in question we could see that now the filtering in the query seems not to allow wildcards any more?
Until now we‘ve been able to apply a filter based on a „contains“ condition and then using wildcards (e.g. „Gi*/0/*“ to filter for certain gigabit interfaces on a switch). Now, after the update, we have to reduce the filter to a string without any wildcards, which does not lead to the same result, unfortunately…
Any idea if this is kind of a bug that has been introduced recently, or is this an intended behavior?
Thanks a lot!
Hi Nils,
Thanks for your question!
Nothing significant changed for this feature in 10.4.0 and should still work as before. Our internal tests still indicate that this feature works and I was able to confirm this manually as well.
This leads met to conclude that either:
- there is a system specific difference in the back-end
- there are other parts of your query that influence the result somehow
To confirm or refute the first option, you can manually query (part of) your table with the Client Test Tool, taking GQI out of the equation:
- Open the Client Test Tool
- Connect with the tool to your DMS
- Start a dynamic table query
- For “Filter(s)” enter e.g. the following: fullFilter=(X == *Gi*/0/**)
where X is the parameter ID of the parameter table column you want to filter on. This is how GQI would send the filter to the back-end - Request the first page and verify if this still works as expected.
To confirm or refute the second option, you could create a minimal version of your query in the app with only the Parameter Table by ID data source followed by your wildcard filter.
Important note!
Using wildcards in a contains/equals filter is a legacy feature that we eventually want to fully replace with the more generic alternative: regex filtering.
This is because wildcards only work for parameter tables and nothing else.
Unfortunately, regex filtering is in 99% of cases not compatible yet with parameter table wildcards.
For now, if it all possible, try to avoid using wildcards.
I don’t have a full view over your use case, but maybe it is somehow possible to use 2 separate contains-filters on e.g. “Gi” and “/0/”?
Don’t hesitate to reach out if you need any more assistance.
Hi Ronald,
thanks a lot for your feedback! I tested the first procedure, and the manual query via Client Test Tool including filtering as described works nicely. So that’s alright.
I then looked into the query once again to see which other element of the query may cause the trouble. And it turns out that there is a “Sort by” just ahead of the filtering which is somehow interfering with it. Once I delete the sorting, then the filtering including wildcards works just fine again!
So, very good that you pointed in the right direction – cheers!
BR
Nils
P.S.: thanks as well for the heads-up regarding filtering based on regex.