Patrick Boucher ftrack

Hi Kanstantsin, Which documentation are you referring to? The file uploaded to the ftrack server and then transcoded for web playback isn't tied to the `Task`. It is a `Component` that is connected to the `AssetVersion`, which in turn is connected to the `Task`. Please let me know if this document that outlines key publishing concepts helps out. Regards, Patrick

Hi Kanstantsin, You may be looking for the `asset_version.encode_media()` method if you want the file to be handled automatically by our cloud transcoder to have a web-playable piece of media and thumbnail created for you. https://ftrack-python-api.rtd.ftrack.com/en/stable/example/encode_media.html#example-encode-media Regards, Patrick

Hi Kanstantsin, If you get a duplicate record error, you have created another asset with the same name connected to the same parent. If you intend to create a new version of the same asset, you should instead load the existing asset and attach your new version to that. I'm attaching a Jupyter notebook that hopefully explains how to do that. Regards, Patrick forum_2205.ipynb

Hi Fernando you are correct that `appointment` record creations and deletions is where you should be looking. As for including the ids in the task's update event, I can log this as a feature request on your behalf. Regards, Pat

Hi Yanelis, Could you tell us where this screenshot is from? Time logging has not been supported in Connect for a while because it was moved to the web application. The current state of time tracking is documented here: https://help.ftrack.com/en/articles/1040447-tracking-time

Just for completeness' sake, an ftrack engineer chimed in on the subject, and I'm leaving a link here as a reference: https://github.com/ftrackhq/ftrack-javascript/issues/73

Hi Evan, Which documentation are you referring to that mentions `<` and `>`? I want to check it out and ensure it accurately reflects current capabilities. As for your initial question, it is my understanding that anything past the boundary of a list is not accessible via the dot notation in a subscription. This would preclude you from accessing `changes.statusid.<new|old>` and `keys.statusid`. These kinds of things need to be implemented in your callback. Regards, Patrick

Hi Fernando, The documentation on handling ftrack events can be found here: https://ftrack-python-api.readthedocs.io/en/stable/handling_events.html#subscribing-to-events https://help.ftrack.com/en/articles/1040479-events Currently, the subscription can't specify any filtering on record data. That needs to be handled by your callback. Regards, Patrick

Hi Walt, That is currently not possible. We don't have a button UI element besides the default submit button (and cancel via the `X` in the top right). I've submitted a feature request on your behalf for consideration by the product team. In the short term, depending on your objectives, implementing your tool with another UI framework (standalone app, external web app embedded in ftrack or not) may be a better solution if its requirements exceed current capabilities. Cheers, Patrick

Hi Walt, That is currently not possible. When using ftrack's simple UI functionalities available via the event hub (https://help.ftrack.com/en/articles/1040465-actions#:~:text=Read more here.-,User interface,-When an action). Using this method, no logic can be sent to change the UI dynamically and no message is sent back for you to process until the form is submitted. This makes it impossible in the current system to create a dynamic UI that refreshes "on_change". I've submitted a feature request on your behalf for consideration by the product team. In the short term, depending on your objectives, implementing your tool with another UI framework (standalone app, external web app embedded in ftrack or not) may be a better solution if its requirements exceed current capabilities. Cheers, Patrick

Release notes can be found here: https://help.ftrack.com/en/collections/133837-release-and-migration-notes#studio If / when OpenAPI support lands, it will be announced here with release notes. To be clear, this is a feature request for now and not currently on the roadmap until the product team prioritizes it, and as such, I can't provide an ETA for the feature.

There is currently no support for the OpenAPI specification. I have created a feature request with the product team on your behalf advocating for support of this specification.

Awesome, Pol. I'm happy you've got things running and thanks for letting us know. Have a great week! Patrick

Hi Pol, Off the cuff, it looks like you're missing `user_security_role` in that projection chain. Could you try: select name, user_security_role_projects.user_security_role.user from Project Regards, Patrick

Hi Samuel, As I understand things, it is not possible to project to get only certain custom attributes. If I were you, I'd explore fetching your tasks without the custom attribute values and then getting the few custom attribute values that interest you in a second pass. For example, once you have your tasks you could do something like: cac = session.query('CustomAttributeConfiguration where label is fps_h').one() cav = session.query(f"CustomAttributeValue where entity_id is {task['id']} and configuration_id is {cac['id']}").one() Obviously this is Python, which is what I was testing with, but you can easily adjust to taste. You can also obviously query for `CustomAttributeConfiguration` records based on multiple keys or labels based on your needs and then query for `CustomAttributeValue` records based on multiple `entity_id` based on your task query and multiple `configuration_id` based on your `CustomAttributeConfiguration` query. I'd encourage you to profile both approaches to see if the second would get you gains based on your particular circumstances. If your use case isn't dynamic in nature, you could also forgo the `CustomAttributeConfiguration` query by "hardcoding" those ids in your `CustomAttributeValue` query in a similar way you're doing it for `type.id` in your `Task` query. Cheers, Patrick