Forum Discussion
4 Replies
- MarkShnier__You
Qrew Legend
Actually the bottom of this help article does explain the comparison operators.
https://help.quickbase.com/api-guide/do_query.html
------------------------------
Mark Shnier (YQC)
mark.shnier@gmail.com
------------------------------- MikeTamoushQrew EliteInteresting. It seems my guess on HAS and CT was correct. It specifically says not to use CT on multi select text field, yet I did and it worked perfectly...wonder why...
I'll change it just in case!
------------------------------
Mike Tamoush
------------------------------
- QuickBaseJunkie
Qrew Legend
Thanks for the shoutout @Mike Tamoush
The way I think about HAS vs CT (right or wrong) is HAS is for a text list fields where you may have values like.
- Approved
- Approved with conditions
- Approved on a limited basis
Using CT.'Approved' would get a positive on all 3 as all 3 contain "Approved."
vs HAS.'Approved' which would only match on the complete match of "Approved".
For TV, that is used with fields that have multiple properties like User. A user field contains the user ID, the user name, and the user email.
When using this operator you can 'mix and match' such that you don't have to only compare an email field to an email value, you could use TV and compare an email field to a user field.
For anyone interested in learning about Quickbase Queries, here is my video (and more is available on https://quickbasejunkie.com/blog).
------------------------------
Quick Base Junkie
------------------------------- MarkShnier__You
Qrew Legend
.. so I think that HAS is similar to a report filter where you want to filter on a Multi Select field and it says "includes" as the filter comparison operator in the report filter. I just did an old style report for "incudes" in a multi select field and used the More .. to show the expanded URL and that translated to a Query with "HAS". Also with a filter on a userid it translated to TV
query=({'201'.HAS.'Curly'}AND{'4'.TV.'yourcoach'})
So it all makes sense now that there's a one to one relationship between the way a report filter works and how that translates into the Query Syntax.
------------------------------
Mark Shnier (YQC)
mark.shnier@gmail.com
------------------------------