Tim Edelmann

ah.. ok thats good to know! I'm glad, this work around does the trick. thank you.

Additional information: We noticed, that the ids look different and we don't know why?? normal ids look like this: '75b59aae-e1bb-11e7-ad88-7ab7a47c9dda' while the one retrieved here looks something like this: '75b59aae-e1bb-11e7-ad88-7ab7a47c9dda_48' this '_48' breaks it! PLUS: The 'entityType' given in 'event['data']['recordData']['entity']['entityType']' is not starting with a Capital letter, which breaks it too! So if we remove the '_48' and use 'TypedContext' instead of the given type, we're able to query the object. Could anybody give us some more insight here? Thanks again

Hey everybody, while setting up a dynamic-enumerator-action, we noticed, that the information on the currently selected element doesn't help to retrieve an actual object. We always get 'None' as a result. This is the event, that comes in: { "topic": "ftrack.dynamic-enumerator", "source": { "id": "c73c09beff154613ba61300782bb836e", "user": { "username": "TEdelmann", "id": "75b59aae-e1bb-11e7-ad88-7ab7a47c9dda" } }, "target": "", "data": { "attributeName": "Briefing_Workflows_00_Maya_Config", "sorters": [], "filters": [ { "disabled": "True", "property": "name", "root": "data", "initialConfig": { "disabled": "True", "property": "name", "root": "data", "id": "ft-dynamicenumerator-2000671-query-filter" }, "id": "ft-dynamicenumerator-2000671-query-filter" } ], "query": "", "groupers": [], "recordData": { "changes": {}, "entity": { "entityId": "883b74ea-132b-11e8-ae79-7ab7a47c9dda_15", "entityType": "task" } } }, "in_reply_to_event": "None", "id": "27304c3ea333491fa793b457e91f7966", "sent": "None" } As you can see, there is given an entity in 'recordData'. But for some reason, we can't query or get the actual object from it. This is what we tried so far.. obj_type = event['data']['recordData']['entity']['entityType'] obj_id = event['data']['recordData']['entity']['entityId'] # obj_id = event['source']['id'] # selected_object = self.session.get('TypedContext', obj_id) # selected_object = self.session.query('Task where id is "{0}"'.format(obj_id)).first() selected_object = self.session.query('{0} where id is "{1}"'.format(obj_type, obj_id)).first() selected_object is always None. any suggestions? How are we supposed to get the current selection, when reacting on 'topic=ftrack.dynamic-enumerator'? Alternatively, it would be very helpful, if the information on what is currently selected, coulde be retrieved in a general way (i.e. like session.getCurrentSelection()) thanks a lot in advance Tim

BUMP! We cannot get this to work or we do not understand, how this is to be used. When executing the example above, we can't see anything in the calendar (which is what we expected). Mattias you wrote: "I suspect that this happens because the event is neither attached to user or a project." Sounds like, we can attach a calendarEvent to a user? Thats what we'd like to do. What is the property-name to provide when setting a user-id? In the sample above 'project_id' indicates attaching to a project. Where is this documented? Thanks.

Hey Mattias, thanks for the quick response! This could be a solution, but we might want to omit one or two of the fields presented in the creation-dialogue..

Hi everyone, on our path to integrate ftrack in our pipeline, we would like to alter the "Create Project" dialog, that pops up, when one clicks on the corresponding button in the web-interface. We already found out, that its possible to set an override, which lets us setup a custom solution from scratch. But since we want to achieve the same look and feel of the original dialog, we thought about using its code, but weren't able to find it. Is there a python script somewhere, which creates this dialog? If yes, where is it? Thanks in advance. The only alternative would be to re-create the whole dialog on our own and then add, what we need..