Mattias Lagergren

Administrators
  • Content Count

    1,081
  • Joined

  • Last visited

  • Days Won

    89

Everything posted by Mattias Lagergren

  1. A possible solution is of course to add an event listener and display an action interface message to the user. You could also remove the time log in the same event callback
  2. Hi Remus, it is currently not possible to disable that but I will raise the issue with the team.
  3. Hi Paul and welcome to the forums. This is an example of how to se the ContextCustomAttributeValue, the first id in the entity_key is the custom attribute configuration id, the second one is the project id. {"action": "update", "entity_data": {"__entity_type__": "ContextCustomAttributeValue", "value": "31"}, "entity_key": ["d25219d6-acb5-11e1-8668-f23c91df1211", "32580850-64a2-11e7-a4bd-0a580ae40187"], "entity_type": "ContextCustomAttributeValue"}
  4. The issue with update events on hierarchical custom attributes should be fixed in an upcoming maintenance release (scheduled for 3.5.25)
  5. Hi Tim, Sorry for the confusion on this - you're correct, the id is wrong when accessed from the sidebar. To work around this you can do the following: if '_' in entityId realId, junk = entityId.split('_') As for the entityType - this is old style entity type from the backend. Instead of using 'task' you would want to use 'TypedContext' on the session: session.get('TypedContext', realId)
  6. Hey Erik, this is something that we're considering for the future. It could very useful if you have a lot of tabs open for different projects.
  7. Yes, the latest replied to note will be at the top. About ingesting them in a sorted manner the problem is likely that they are added too fast or at once. A possible solution is to explicitly set the note['date'] to order them. E.g. by offsetting them in seconds.
  8. Hi and welcome to the forums! There are multiple ways to achieve this, either by using our API and build an action for it. Or setting up a "template" and just copy and paste the structure from it. And a template project is an ordinary project that you have decided should only be used to copy&paste from (could be hidden or named to indicate that it is meant for templating)
  9. Hi Luigi, as of now the best way would be to temporarily re-activate the project and run the report
  10. Hi and welcome to the forum. The Collection object that you get can be accessed much like a list: for note_component in some_note['note_components']: ... some_note['note_components'][0] et.c
  11. Hi Ozen, I remember us discussing this and we're tracking a feature request about it. I will forward this to the team
  12. I will report this as a bug (hierarchical attributes appearing on user in UI but not in API) We've just recently got a bug report about ftrack.update events no triggering when an hierarchical attribute changes.
  13. Absolutely, documenting this better is something that we would like to do. And also update it to follow the new schema and property names so that it is more in line with the rest of the API.
  14. Hi Tim, I've tried with the script that you provided and it works 100% of the time for me. If you run the above script as it is with no other actions/event listeners in the same script/python process, does it still only work 30% of the time? If you add a print or two in the launch method, does it seem to get called (trying ot locate if the issue is in the UI or in the python api)?
  15. I'm afraid that the functions can only run on Task custom attributes and not no the Shots
  16. Hi Tim, Could you provide a small script to reproduce this issue along with some steps that you take in the UI? Please make the script self-contained and return a static list of options so that I can run it here and help you debug the issue.
  17. The FTRACK_CONNECT_PLUGIN_PATH should be set when launching connect if you want to change where it searches for plugins. The FTRACK_EVENT_PLUGIN_PATH is only recommended to set when you publish from your own scripts. You must add the path to sys path: https://bitbucket.org/ftrack/ftrack-example-location/src/114a8deeb307de10bc479c3cdeb0a857f842522d/hook/connect_plugin_hook.py?at=master&fileviewer=file-view-default#connect_plugin_hook.py-12
  18. Hi Jerome, we have hidden it from bitbucket because it is not officially support / maintained. If you want I can give you access - please email support@ftrack.com and refer to this thread.
  19. Thank you for taking the time to share this, I will pass it on to the team!
  20. Hi and sorry for the confusion - I've replied here: In short; using Connect is not necessary for publishing to a location. If you want to use Connect's stand alone publisher UI, start integrations with the locations available, have the path resolved in the UI, et.c. then you can use Connect for this.
  21. Hey, sorry for the confusion. There are two things here - one is the location and publishing to it. The other one is the file path being red/not resolved in the web UI. Publishing files to a location / custom location does not require ftrack Connect - it is done only through the ftrack API. (If you want to use Connect and it's built in publisher, or use the integrations, you will need to make the location available to Connect/Integration. This can be accomplished by adding it as a plugin to Connect.) Resolving paths in the web UI - this requires a script listening to the ftrack.location.request-resolve from the event hub. Connect already does this and will resolve any location that it knows about. The link I gave here: https://bitbucket.org/ftrack/ftrack-example-location can be used as a boiler plate to make a Location and have it act as a plugin to Connect. This is not necessary if you just want to publish to it from a Script. But good if you intend to have your users run Connect to publish, start integrations and resolve paths. Using the unmanaged location means that the files are never copied to the new location - you just register them where they already are.
  22. Are you using Connect? If you add the location as a plugin to Connect it should be properly resolved in the web UI. I recently created an example here with some information on how to get started with it in Connect: https://bitbucket.org/ftrack/ftrack-example-location
  23. There are a few things that depend on the work day length like forecast in Overview, and Bid estimate if you switch between days and hours settings. Yes, some customers are not comfortable with these automatic reminders so you can always turn them off and use reports to see if you should remind someone "manually".