Remus Avram

Can you please invite [email protected] as well?

Hi Johan, is there any plan to implement this soon?

Hi all, is there any update regarding this? This will help a lot our production to keep all the tasks and the information in one place, Ftrack.

I think this is what exactly we are looking for we will give it a try and let you know if works for us

Hi @Mattias Lagergren any updates regarding this? This will help us a lot if we were able to send messages to Artists using the Ftrack notifications.

Thanks @Mattias Lagergren for your quick answer! The checklists are useful for us for the big shows.

Hello, the only documentation which I found is this: http://ftrack.rtd.ftrack.com/en/stable/using/communicating/using_notes.html#using-communicating-using-notes-note-completion. But this is a note completion, not a checklist / todo list. Does anybody know if the checklist / todo list was implemented?

Hello, is this already implemented? I don't find any documentation how to use it. Cheers, Remus

Can you please add me, too my email address is: [email protected]

Thanks for the info! We will try to test this, too.

We already requested this. It makes sens for us as using multiple session it means creating multiple cache files which increase the number of queries to the DB.

We tried multiple ways. It will not work. If you are using multi threads, use multiple session.

Thanks @Martin Pengelly-Phillips for your info. I am interested how others studios are using the `ftrack_api`.

Thanks @Martin Pengelly-Phillips for the info! So as I understand the cache is build per session. If there is a session per thread, then for each thread there is a cache file which can contain the same data as the other sessions. Am I correct? Having only one session, there is only one cache file with all the data and the queries are faster. Less queries to the database. Do you know if the sessions connected? I did a test and it seems that they are. I query in assetBuild in one session and I created a task using as parent the assetbuild from the other session and the task was created. @Martin Pengelly-Phillips: I am interested how are you using the session. Are you creating a new session for each query / commit?

Thanks @Mattias Lagergren for your answer! For us it's quite important because we are planing to use threads in all of our tools. We would like to use at least 1 thread in order to not freeze the UI while it is fetching the data. You mean something like this: from multiprocessing.dummy import Pool as ThreadPool import ftrack_api from ftrack_api.symbol import Symbol session = ftrack_api.Session() def check_keys(entity): for key in entity.keys(): if isinstance(entity[key], Symbol): print entity, ': ', key def check_children(entity_id): entity = session.get('TypedContext', entity_id) if 'children' in entity.keys(): for child in entity['children']: check_keys(entity=child) check_children(entity_id=child['id']) def main(): projects = session.query("Project").all() projects_id = [project["id"] for project in projects] pool = ThreadPool() pool.map(check_children, projects_id) if __name__ == "__main__": main() It still doesn't work. In the thread most of the time session.get('TypedContext', entity_id) returns None.