1. Company news

    1. 5
      posts
  2. ftrack Studio (main app)

    1. 827
      posts
    2. 988
      posts
    3. API

      1,160
      posts
    4. 485
      posts
    5. Actions and Widgets

      Extending the functionality in ftrack with custom Actions and Widgets - read more at ftrack.com/actions

      197
      posts
    6. ftrack Go

      Discussions about ftrack Go for iOS and Android

      14
      posts
  3. Connect (plugins)

    1. 322
      posts
    2. 127
      posts
    3. 260
      posts
  4. Reviews

    1. 78
      posts
    2. 93
      posts
    3. 24
      posts
  5. Tech preview

    1. New integrations

      Discussions of the new tools that will replace current Connect integrations into Nuke, Maya, 3DS Max and other applications.

      27
      posts
    2. 29
      posts
    3. 1
      post
  6. Jobs board

    1. Job listings

      Looking for a pipeline TD, developer or production manager? Post your job listings here.

      3
      posts
  • ftrack Status

  • Who's Online (See full list)

    There are no registered users currently online

  • Recent posts

    • Yes, I want do it for performance reasons.
      I will need to get a list of version for all assets in task groped by assets. I did it something like that: import ftrack_api from itertools import groupby session = ftrack_api.Session() entity = session.get('Context', '376a3498-1191-11e8-8917-001e582bf738') assets = session.query( 'select asset.name, version from AssetVersion ' 'where task_id is "{0}" and asset.name is_not ' 'none order by version desc'.format( entity['id'])).all() res = [{"asset":l, "versions":list(v)} for l,v in groupby( sorted(assets, key=lambda x:x['asset']['name']), lambda x: x['asset']['name'])] But usually I working only with latest ones and rarely with previous.
      So in that reason I thought that's will be great to get only latest versions and how to get this list in best performance way.
    • Not possible at present to do in one query.  Are you wanting to do it in one query for performance reasons?  The API does support batching calls under the hood, but it doesn't seem to be implemented for queries yet. There are some TODOS in the code though... def _query(self, expression): '''Execute *query* and return (records, metadata). Records will be a list of entities retrieved via the query and metadata a dictionary of accompanying information about the result set. ''' # TODO: Actually support batching several queries together. # TODO: Should batches have unique ids to match them up later. batch = [{ 'action': 'query', 'expression': expression }]
    • Yes, correct - it will send out if the logged time is < than the workday length. I'm afraid there is no option to set it different from the workday length.
    • It seems that ftrack wants to send reminders when a user has logged less then 8 hours(i'm assuming this is the quantity specificied in the workday length field). Is it possible to set the minimum time required to send a reminder without affecting the 'workday length -> hours' exchange rate? G