A common request has been to allow sorting, grouping, and/or filtering on Query fields. Examples are numerous, but a few include:
Double yes please. : D
It would be great if you could also apply color formatting rules to Query fields as well!
For example, if you have a query field to tally the number of assets, or FX shots in each episode, then you can set up a color formatting rule to highlight the cell if it's greater than a certain value.
Yes please. This feature request is a big one.
Our studio would love to have this. We have query fields on our assets page for the earliest animation start date and latest animation end date for all shots using that asset. Production would love to be able to sort these for planning purposes.
+100 please, oh please. we have almost 100 query fields within our server; 35+ in our Shot Entity alone. having the ability to do anything with that information would be a tremendous addition to it's capabilities. thank you in advance!
+1
I'm opening a support ticket looking for a workaround on what I'm trying to accomplish here (filtering on pipeline task status summary).
+5 here!
+1
+1
+1
Yes please in the name of a whole team. We would really like to be able to apply color formatting rules on query fields.... Open notes count.... Pretty please....
A big Yes here as well!
I'd appreciate to sort assets by number of shots it is linked to, for example.
I know SQL joins are a bear, but this is sorely needed. We rely more & more on calculated fields in order to keep things DRY. In the end, the data is only as good as our ability to make it legible.
Exactly. We're doing the same. I throw up in my mouth a little every time I have to write yet another event daemon to bake the value of what we're already returning with a query field because another developer or a user needs to sort or filter or group by it.
As an alka-seltzer... if any of you are hosting-your-own Shotgun install and thus have direct PostgreSQL access, I've written a little python method that grabs the filter conditions and summary type stored on query field properties with psycopg (with assists from yaml and json) then rewrangles them through an appropriate sgAPI .summarize or .find_one -- so I can retrieve the values of query fields with python without apriori knowledge i.e. having to duplicate the query config in python code. PM me if you'd like a copy; it's v1 and so it doesn't support all possible return types yet, but it's a good start and serving our purposes for now.
Yes please!! This would be so helpful.
+1!
Yes! This sounds great!
Yep, just opened a ticket about this and was referred here. +1
Another "yes please". We're using a query field for our episode thumbnails, and we'd like to have logic that looks something like:
- If there are any animation renders, show the latest one.
- If there are no animation renders, show the latest Leica.
- If there are no Leicas, show the latest script.
Thanks.
Hah, just realized in looking back at the original post that I was referred by Shotgun helpdesk to this "feature request" a month ago - and the request has been open for five years! Anyone instructed to follow this thread back in 2013 must be so over this at this point.
サポート