Are we ever going to get the ability to filter by Query fields? People have been asking for this for at least a decade, and we still don’t have it. Why has this never been implemented? It basically makes Query fields useless except for display purposes.
I always have to come up with ridiculous work-arounds just to see simple information generated by a query field. It’s mind boggling that after all these years that it’s still never been implemented.
Sorry if I don’t read as nicely as I’d like to, but this has been costing me time and money for several years. And it just burned me again.
Based on experience with other database systems too, I expect the query fields aren’t stored values, but values calculated only when the user triggers them to evaluate to display on the layout and, as such, they don’t have indexes. Without the index, the filter or sorting features would be impossibe (or so slow as to make us - and all our users - cry).
Exporting a found set to csv and sorting or filtering a set of records from there could work. Other times, when I want this behavior, I set up another field and have an event plugin trigger to populate it as a stored value. It is more work upfront, but more reliable and flexible for how we might want to use it.
In addition, as a stored values your users may see some other benefits:
less of the “Calculating…” values when loading a large page with slow claculations/queries
we have seen use cases where the query fields were too slow to allow a found set to export to csv, but the exports worked great once the values were calculated and stored by the event plugin instead.