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 file doesn’t exist and notify someone that something failed. It’s important to enable faster debugging when something goes wrong. Sometimes it’s not clear from the point you get the details on what you’re going to do with them. Always add a comment.Ī good commend here is not what you’re getting but why you’re getting it. 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 important so that you know, without expanding the action, the plan that you’re getting the information and corresponding group (if it’s important in this case). You can even follow up with a flow to send notifications for completed tasks in a specific bucket.Here are some things to keep in mind. Just add the Ids to each of the items and it’ll work in the same way. If you’re creating tasks only in a single plan, you can preselect it in the action and store only the ‘bucketId’ in the sheet.Īnd it’s not limited only to Excel files, you can use the same solution also to import tasks from a SharePoint list. It’s also not necessary to store all the values in the import Excel sheet. But IDs stay the same from the moment you create the group, plan or bucket. It’s because names can change, and a small change in the name could break your flow. It’s important to understand that Power Automate doesn’t work with names, it works with IDs. The solution above describes how to use Power Automate to import Planner tasks from Excel into various groups, plans and buckets. "planId": "S4VCKKcv60CO-f_TtS-GhJgADSVZ",įind the right bucket by its name, take its ID and add it to your Excel import file. "W/\"JzEtQnVja2V0QEBAQEBAQEBAQEBAQEBARCc=\"", ![]() Among it will be the bucket ‘name’ and the ‘bucketId’ (under the ‘id’ key). If you add the action to your flow and run it, you’ll see in the run history all the available buckets and their information. But you can use the Power Automate action ‘List buckets’ to get it as a workaround. It’s not so simple with ‘bucketId’ as that one doesn’t appear in the url. PlanId=S4VCKKcv60CO-f_TtS-GhJgADSVZ Get the bucketId Just open the plan in your browser and take it from there, ‘groupId’ is after ‘groupId=’ and ‘planId’ after ‘planId=’. The ‘groupId’ and ‘planId’ are easy to get from the url in the plan. To import tasks from an Excel file into various plans/groups/buckets you’ll need their ID. There isn’t any name except the task title. There’s a ‘groupId’ for the M365 group, ‘planId’ for the plan and ‘bucketId’ for the bucket. You can see that if you configure the ‘Create a task’ action and then switch to ‘Peek code’. Power Automate works with the IDs of the Planner groups, plans and buckets, not with their names. But what if you don’t want all the tasks in the same plan/bucket? If you want to use a single Excel file with all the tasks for multiple plans and/or buckets? How can you tell Power Automate which plan and which bucket to use for each of the tasks? Use the group/bucket/plan IDs ![]() Every row in the Excel table will be taken and imported into the predefined plan and bucket. I already published a post on importing tasks from Excel to Planner with Power Automate, but the solution is importing all the tasks into the same place. “Is there any way I could fill-in buckets and plans directly in an Excel sheet so I could use only one file to create Planner tasks in as many plans as I need with Power Automate?”
0 Comments
Leave a Reply. |