{"id":14393,"date":"2020-07-03T06:48:58","date_gmt":"2020-07-03T04:48:58","guid":{"rendered":"https:\/\/www.dbi-services.com\/blog\/microsoft-teams-power-automate-and-planner\/"},"modified":"2024-09-11T15:07:52","modified_gmt":"2024-09-11T13:07:52","slug":"microsoft-teams-power-automate-and-planner","status":"publish","type":"post","link":"https:\/\/www.dbi-services.com\/blog\/microsoft-teams-power-automate-and-planner\/","title":{"rendered":"Microsoft Teams, Power Automate and Planner"},"content":{"rendered":"

As we moved to Teams at dbi and one of our customers, automating tasks was a strong need.
\nOne of the tasks that could be automated is the creation of tasks in Microsoft Planner which does not support recurring tasks. Every 4 weeks, we are patching the environment. For everyone awareness and follow up, we need to publish these dates in the planning. As the pace of these tasks is known, it is a bit repetitive to create these tasks manually.
\n
\nMicrosoft Power Automate (previously known as Flow) is powerful tool to automate tasks and it integrate natively with Teams. My idea was to create 4 tasks just by providing the first date and then creating all of them on a 7 days interval.<\/p>\n

Flows Overview<\/h3>\n
    \n
  1. Initialize indice<\/strong> to 1. We will use it to iterate<\/li>\n
  2. Initialize a First Day of Cycle<\/strong> object based on user input<\/li>\n
  3. Initialize an ArrayOfEnv<\/strong> which will be used for naming each task. For example, array can contain:\n
      \n
    1. Sandbox<\/li>\n
    2. Dev<\/li>\n
    3. Test<\/li>\n
    4. Prod<\/li>\n<\/ol>\n<\/li>\n
    5. Then create a loop and iterate until we reach 4\n
        \n
      1. Creation of the task with\n