I have a template, and a template that you can use that will help you make your Flow resistant to issues. It’s horrible to have failing Flows in Power Automate since they may go unlooked for a while or generate even worse errors. Have your Flow fail graciously when the task doesn’t exist and notify someone that something failed. It’s important to enable faster debugging when something goes wrong. Indicate where the task that you’re trying to get (or the context). Always add a comment.Īdding a comment will also help to avoid mistakes. Always build the name so that other people can understand what you are using without opening the action and checking the details. The name is super important in this case since having only “get task details” doesn’t tell us much. Never try to generate the ID yourself since they may change, and then your Flow will fail. Never generate the ID yourself.Īlways get the ID either from a trigger or from another action. We never know when we need them, so it’s better to ignore them than not have them.
Some of the fields may not look useful, but we’re glad that they are returned. Finally, you have the name of the user that created them. We have the type (checklist), the order, title, and if it’s checked for the checklist items. Here’s an example for two checklist items: [
You can use these values in Power Automate for your automation.
Each has its priority in the list, the information of the user, the link, and the alias to display in the task. "id": "b6a1A137-2a63-4713-b3b9-1a43ba47A9fb"Īs you may have noticed, there are no attachments stored in Planner. "resourceLink": " Partilhados/small-Screenshot_at_18_35_34.jpg?web=1", Here’s an example for two references, the first an URL and the second a file that we upload to the task: [ I’ve added a few items and attachments, so this is what we’ll get:
0 kommentar(er)
