hi @v-bacao-msft,
I discovered a bug using the v2 version of the Todoist connector.
The trigger When a task is completed (V2) (Preview) returns this body
{
"content": "Stretching & Breathing",
"meta_data": null,
"user_id": 5123746,
"task_id": 3463747610,
"project_id": "2215864327",
"completed_date": "2019-11-05T08:35:51Z",
"id": "3356452419"
}
Consuming the result in a next step, into the property itemTaskId, I got the value of id, and not task_id.
I don't know what is id, but I need the task id.
The current error message is:
Could you please fix it?
Solved! Go to Solution.
Hi @mirkobersani ,
You could get task id via expression:
Best Regards,
Thanks for reporting the issue. It seems the action internally sends request to the Todoist Sync API documented here: https://developer.todoist.com/sync/v8/#get-all-completed-items. I have requested the engineer who worked on the V2 action to take a look, and will update you once I get a response.
Do you know a situation when the content of 'id' and 'task_id' properties be different? Since, the example in the documentation page shows same content of both 'id' and 'task_id' properties.
Update: We do not know when the values of two properties will differ, and when they do, what each of those two values signify. I have sent a request for clarification to the Todoist service.
As far as I know, the most relevant one is task_id.
Apparently id is useless, but ask Todoist for confirmation.
They have just updated the main version of the software and it could be a new subject.
@mirkobersani - Can you see if following workaround works? I haven't tested it so please let me know if you see any error.
Add 'Parse JSON' action to the Flow. Set the 'Content' field of action to 'A Todoist Items response object'. For schema, select 'Generate from sample' and use a response similar to below:
{
"items": [{
"content": "Stretching & Breathing",
"meta_data": null,
"user_id": 5123746,
"task_id": 3463747610,
"project_id": "2215864327",
"completed_date": "2019-11-05T08:35:51Z",
"id": "3356452419"
}
]
}
Then you should be able to access 'task_id' property and perform other operations within an 'Apply for each' action with 'items' selected from 'Parse JSON' action output. See below screenshot:
Hi @mirkobersani ,
You could get task id via expression:
Best Regards,
The first Microsoft-sponsored Power Platform Conference is coming in September. 100+ speakers, 150+ sessions, and what's new and next for Power Platform.
Announcing a new way to share your feedback with the Power Automate Team.
Learn to digitize and optimize business processes and connect all your applications to share data in real time.
User | Count |
---|---|
3 | |
2 | |
2 | |
1 | |
1 |
User | Count |
---|---|
5 | |
3 | |
3 | |
2 | |
2 |