Leaderboard

A small update for everyone listening here: I've made the first steps for creating the Gantt-exporter. It's not finished, but might be sufficient for some of you already: https://github.com/TDArlt/ftrack/tree/master/ftrack-connect/export-gantt-chart I will keep you updated 🙂

The Python API Client often uses relationships (e.g. status) to update entities, but when using the raw API backend or the JS API client I recommend that you instead the relationship key attributes instead. In this case, that would be `status_id`. A more complete example of a request body would be: [ { "action": "update", "entity_type": "Task", "entity_key": [ "12bd29be-72b0-11e7-96a7-0a580ae40a16" ], "entity_data": { "status_id": "44dd9fb2-4164-11df-9218-0019bb4983d8", "__entity_type__": "Task" } } ] Regards, Lucas

Hi and thank you all for your feedback. We understand the motivation for validating input and will take this into consideration for future development. As I understand it and what I've heard from other customers is that the project code, but also shot / asset / task names should be validated. A suggestion in the first post is to have a regexp to control this, what do you think about this? Would that be enough for your use-cases? Thank you for highlighting this. The ftrack.validate event is deprecated and we will make sure to remove it from the documentation.

We are incredibly pleased to announce that today, Cospective, creator of the Academy Award and Emmy-winning synchronized remote review tool cineSync, has joined forces with ftrack! We have enjoyed a close working relationship with Cospective since 2015. During that time, we’ve developed a deep integration that links cineSync with ftrack Studio, and a working relationship with the Cospective team that has flourished over the years. We’ve partnered with Cospective at industry events, shared many meals, and grown as both friends and colleagues. For us, Cospective was the natural choice for a partner. The company mirrors ftrack in its professionalism, creative aspirations, and spirit of innovation, and in cineSync, Cospective has built a robust and industry-changing product that continues to find new ways to simplify and streamline workflows for creative professionals all around the world. Cospective’s ambitions align very firmly with our own, and we are extraordinarily proud to bring both its people and products under the ftrack umbrella. You can learn more about this landmark acquisition and what it means for this new chapter in the ftrack (and Cospective!) story below. Read the full story about ftrack's acquisition of Cospective

Soo. I went ahead and created an Ftrack Slack User Group. However there's this small problem I haven't realized till now. Slack is not very good with public access, so every person needs to get an invite (or be within a specific domain, which is even worse). There is this lovely service called slackin, but that of course needs to run on something. Right now I'm ok with just sending out invites like crazy if anyone asks here to get it going. Theoretically as it grows this won't be an issue, because any member can send an invite. It'll just be a bit of a hassle at the beginning. Maybe ftrack guys would be interested in hosting this tiny slackin service, to make it easier? Anyways the address is: ftrackusers.slack.com Come join the party... (it's very, very lonely right now )