New feature - Advanced filter queries
3 3

5 posts in this topic

Check out this new blog post from our Senior Developer Mattias Lagergren about using our powerful API query language in the ftrack UI to slice and dice data in spreadsheet.

https://www.ftrack.com/2016/04/advanced-filter-queries.html

Let us know how you would like to see this evolve.

Cheers,
Fredrik

Share this post


Link to post
Share on other sites

Hi,

These filters are really cool.

Is it (or could it be) possible to refer to the user's own id in a filter query? For example, if I input the filter query for a Shot:
 

children.appointments.resource_id is '72d53164-66b8-11e3-a80c-000c29912c4e'

and that gives me all the shots that have tasks that my user is assigned to, which has been requested a lot here. If instead of specifying the id, it could be something like user.id, I could share this filter globally and a lot of people would be so very happy about it.

 

Kat

Share this post


Link to post
Share on other sites

Hi Kat,

It is currently not possible to reference the current user in the query. We have discussed similar substitutions for creating filters with relative dates as well, I believe this could be supported in a similar way.  Thanks for the feedback!

Regards,

Lucas

Share this post


Link to post
Share on other sites
On 6/2/2016 at 0:00 AM, katalina-w said:

Hi,

These filters are really cool.

Is it (or could it be) possible to refer to the user's own id in a filter query? For example, if I input the filter query for a Shot:
 


children.appointments.resource_id is '72d53164-66b8-11e3-a80c-000c29912c4e'

and that gives me all the shots that have tasks that my user is assigned to, which has been requested a lot here. If instead of specifying the id, it could be something like user.id, I could share this filter globally and a lot of people would be so very happy about it.

 

Kat

Hi, a follow-up on this. I've just implemented support for this feature, which we're currently reviewing. The syntax will be:

children.appointments.resource_id is "{CURRENT_USER_ID}"

If nothing critical shows up it should make it into a release soon

Share this post


Link to post
Share on other sites
On 6/3/2016 at 6:21 AM, Mattias Lagergren said:

Hi, a follow-up on this. I've just implemented support for this feature, which we're currently reviewing. The syntax will be:


children.appointments.resource_id is "{CURRENT_USER_ID}"

If nothing critical shows up it should make it into a release soon

That would be perfect!

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
3 3