Lorenzo Angeli

Hi @Damien Keraudren, I have just tested the code and seems to be working fine the following: import ftrack_api session = ftrack_api.Session( auto_connect_event_hub=True ) user = session.query( 'User where username is "{}"'.format( session.api_user ) ).first() ui_event = ftrack_api.event.base.Event( topic='ftrack.action.trigger-user-interface', data=dict( type='message', success=True, message='A message to the user.' ), target='applicationId=ftrack.client.web and user.id="{}"'.format( user['id'] ) ) session.event_hub.publish(ui_event)

@Vladimir Pylev Locations are not related to the web service for web reviwables, but tied more on the desktop or cloud file publish. Is what you are looking for is a way to take control of your online review storage ?

Hi @YuChen looks like you found a bug in our documentation ! The actual action you need to use is : remove_user_security_role not revoke_user_security_role We are looking now into fixing the documentation, sorry for the time you spent and thanks for reporting it! Cheers. L.

Hi @YuChen session._call has been deprecated with api 2.0 SessionPrivate method Session._call() has been deprecated. You should now use the public method Session.call(). could you please what api version are you using ? you can simply check from a shell with: python -c 'import ftrack_api;print(ftrack_api.__version__);' I'll double check the example in the meanwhile with latest api 2.2.0 Cheers. L.

@JP LeDouxyou should be in now.

Hi @Peter Arcara thanks for reaching out and sorry to hear you have been having issues. Few questions for you to try to better help: What version of connect are you using (1.1.2 or 2.0Rc ) ? Are you launching the integration from within connect with a context (task) selected ? Is your version of houdini py2 or py3 ? What os are you on ? (guess Windows) Can you please send console logs messages and ftrack logs ? Looking forward hearing from you. L.

@YuChenCustom AttributeLinks have been introduced in 4.8 , I'd suggest reaching out to our support to get more informations on how to upgrade. Hope it helps! L.

You should now be in @molsontheory

Great to hear @Damien Keraudren!

Hi @Damien Keraudren if what you want is to visually collect similar actions behaviors, you can use the variant https://help.ftrack.com/en/articles/1040465-actions Hope it helps. L.

Hi @Damien Keraudren you approach seems quite right to me. Would you mind sharing the discover method code so we can have a closer look ? Cheers. L.

@Andy C you should be in now!

Hi @db5007 the version of connect you are using does not run py3k applications such as Nuke 13 *. If you want though, we have started a beta program here in the forum where we are providing support for those. Hiero ,in the specific, is still missing but it'll come before final release. If you are interested on joining please head here and get registered ! Hope it helps! L.

Hi @Rory If you haven't I'd suggest having a read on the general syntax about the query system here. And look into details about the query projections to have a better idea on how to optimisatise the queries. In regard of your question: > Certain projnames return a result id/name but others don't ? Projects (as well as any other ftrack entity type) do have some values set and available by default and defined by the server schema, such as id and others. Name can be there or not , but really depends on the entity type (eg: AssetVersion won't, Project will ) The easier way to see what fields are available is to get the keys() off the entity you just got back from the query eg: a_project = session.query('Project').first() # return only the first project found print(list(a_project.keys())) which will return all the available fields available for the project: > ['created_at', 'managers', 'calendar_events', 'color', '_link', 'full_name', 'disk', 'children', 'timelogs', 'end_date', 'parent_id', 'created_by', 'disk_id', 'id', 'user_security_role_projects', 'start_date', 'project_schema', 'metadata', 'status', 'scopes', 'project_schema_id', 'parent', 'descendants', 'thumbnail_id', 'review_sessions', 'appointments', 'link', 'is_private', 'assets', 'is_global', 'name', 'notes', 'thumbnail', 'assignments', 'thumbnail_url', 'allocations', 'custom_attributes', 'created_by_id', 'root', 'context_type'] Hope it helps. L.

Hi @alexisp, at the moment there's no direct call from the api to get the review session url, but can be "easily" generated with the following snippet: import ftrack_api session = ftrack_api.Session() # Retrieve the Review Session you are interested in rs = session.query('ReviewSession').first() # Ensure the shareable link is enable rs['shareable_url_enabled'] = true session.commit() # Get the signed url from the server signed_data = session.call([{'action':'generate_signed_url', 'entity_key':[rs['id']], 'entity_type':'ReviewSession'}]) # Compose the review url shareable_url = '{}/review/{}?signature={}'.format(session.server_url, rs['id'], signed_data[0]['signed_url']) print(shareable_url) hope it helps. L.

Hi @AndyMaurer thanks for sharing back the fixes. Surely will come at hand to many others to have it ! Cheers.

@aline3d you should be in now!

@Toby Angwin @kristin you should be in now. Sorry for the delay !

Hi @MattM, One way of handling this could be to provide a secondary location (with a lower priority than you main one ) to be used to move copy the data you want to archive. Such a solution can also provide various optional features, like archiving only approved data and backup dependent components. Although at the moment we do not provide such a feature off the shelf, our api can provide you all the basic building blocks to build it. Below some resources which can help you getting a grip with those: Location : https://help.ftrack.com/en/articles/1040442-locations Location API: http://ftrack-python-api.rtd.ftrack.com/en/stable/locations/index.html Location Webinar: https://www.ftrack.com/en/intro-to-locations-webinar Actions (to trigger the data archiving) https://help.ftrack.com/en/articles/1040465-actions Actions API: http://ftrack-python-api.rtd.ftrack.com/en/stable/handling_events.html Depending on where you want to archive the data (if not on your local storage) you could also use third party accessors such as the Amazon S3 one to have cloud backups: https://pypi.org/project/ftrack-s3-accessor/ If you want to get your feet wet with Location I also suggest having a look into our Recipes repository for inspiration: https://bitbucket.org/ftrack/ftrack-recipes/src/master/python/actions/multi_site_location/ Hope it helps. If you have any further question please let us know! L.

Hi @Toby Angwin , Nuke studio currently requires a fully managed location in order to work. This because we want to have the files output fully handled from the Location and structure ftrack plugin. > We are using an un-managed storage scenario as we are starting to roll out ftrack across our facility and have an existing folder structure that can't easily be changed. We'll be looking on how we provide such a feature, but cannot provide an ETA atm. One option you could look into is to convert your folder structure into an ftrack structure plugin for your location. Hope it helps. L.

Hi @John Kesig thanks for the suggestion ! We usually prefer to leave these customisation to end users to better match their local workflow. Soon though, there'll be more agile ways to provide what you are after. Cheers. L.

Hi @finnjaegger thanks for the links and the insights. Be ensured Resolve is well on our radar and we are looking into providing a proper integration, there's just no ETA for it. I'll be having a proper look at what resolve 17 brings as it seems quite interesting. Stay tuned! L.

hi @Hadrien FARRE this error often comes from a mix up between python 3 and python2, usually trying to load python2 in python3 interpreter. Also can see you are using python 3.9 , although supposed to be working , we currently support up to 3.8 with a closer eye to 3.7. hope it helps. L.

@matthieu Thanks for the headup on the PySide version! if you are using the pyside2 branch of connect (which is also python3) you should set : FTRACK_API_USER FTRACK_SERVER FTRACK_API_KEY the other legacy envs (such as LOGNAME) have been deprecated in that branch. hope it helps. L.

hi @matthieu, we are actively working on connect for python on 3 .If you like to give it a go , you can try this branch This new version though is not compatible with the current integrations ., but we are working on solutions to make them work back, just not there yet. In regard of your error, seems strange to be coming from the api , as it seems to be referring to Dialogs, which are just a ui thing. There'll be some news soon. Cheers. L.