1. Company news

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

    1. 1,124
      posts
    2. 1,165
      posts
    3. API

      1,503
      posts
    4. 561
      posts
    5. Actions and Widgets

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

      242
      posts
    6. ftrack Go

      Discussions about ftrack Go for iOS and Android

      19
      posts
  3. ftrack Review

    1. 94
      posts
    2. 104
      posts
    3. 26
      posts
  4. Connect and plugins

    1. 352
      posts
    2. Connect package releases

      Notes on the latest Connect releases.

      7
      posts
    3. 144
      posts
    4. 302
      posts
    5. 19
      posts
  5. Tech preview

    1. API

      5
      posts
    2. New integrations

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

      30
      posts
    3. 31
      posts
    4. 3
      posts
  • Popular Contributors

  • Status

  • Who's Online (See full list)

  • Recent posts

    • Sorry to revive an old thread, but is there any way to change the user for the Activity also? The change suggested by @Mattias Lagergren definitely changes the "Published By" property, but the Activities tab for the Asset Version still shows "<api user> published..." instead of the user I specify in the `user_id`.
    • Hi, The filter that you need requires multiple queries. And the web gui can't handle that, at the moment. This is something that we are aware of and that's being discussed. Can't giva any guarantees, but hopefully we could get even better possibilities for queries in future release(s)of ftrack. In the meantime, as mentioned by Julian, you could use the API. Regards, Johan
    • Hey Julian, thank for your reply. Thats a good idea. We will try that. Like you said, it would be very very welcome to do this kind of sorting stuff with filter queries instead. Thanks again. Sascha
    • Ah ok .. guess that’s by design. you could setup an event handler that is listening to status changes and sets a ‘latest_approved’ flag on the most recent approved version. Then you could use that attribute in your queries. Quite involved for what you want but it should work. Would be welcome if something like that could be accomplished with the filter queries instead.