8/17/2023 0 Comments Tasks by planner and todo![]() ![]() Liked this article? Subscribe to my newsletter and get more tips and tricks from the field delivered straight to your inbox. Its simplicity and flexibility make it a perfect tool for everyone including seasoned developers who want to quickly get their job done. Microsoft Flow is a perfect tool for automating all kinds of tedious and repetitive work in Office 365. If all went well, you should now see your tasks created in your plan. In the Tasks input, specify the list of tasks to add to your plan. From the top bar, select the Test button and perform the trigger action. Finally, select the bucket where to put the tasks. As the task's Title, select the Current item dynamic content. Sign in to Planner with your account and select the plan where to create the tasks. To do this, inside the Apply to each step, add a Create a task Planner step. The last step left is to create the actual Planner task for each task from our input. So as a next step, we need to iterate through them using the Apply to each step and selecting the Tasks variable as the object to iterate on. Without it, you will end up with one line and create a single Planner task with all tasks as its title.Īfter this step, our tasks to create are stored in an array. The tricky part, especially if you've done some coding in that past, is that in order to split the input string per line, instead of using \n, \r\n or something similar, you actually need to enter the actual line break, press the 'enter' key on your keyboard. And to do it, you use the split function. To use it further on, you need to break the input into separate lines. The expression reads the value from the text input you created previously, where each task to create in Planner is entered in a separate line. As its Value, set the following expression: Name the variable Tasks and set its type to Array. Next, add a new Initialize variable step. Give the input a name and a description that will be displayed when you start the Flow. This will allow you to reuse the Flow in the future should you have more tasks to import. In the newly created Flow, open the trigger and add a Text input. In the dialog, provide the name for your Flow, and select Flow as the application from which it will be triggered. ![]() You have a Planner plan, you have the tasks, you just don't have tasks in Planner and creating them manually doesn't quite sound appealing. To drive accountability, you want these actions to be in Planner. You attended a meeting, took some notes, you all agreed on some follow-up actions that you wrote down. ![]() Assuming you can use Flow in your organization, you can easily automate many of your daily tasks. It allows you to stitch the different services both inside and outside of the Microsoft cloud together with just a few clicks, without you having to worry about things like authentication or deployment. What macros are to Office clients, Microsoft Flow is to Office 365. But what if all you need to do is to create some tasks in Planner and you don't have the time and money to start a project, write specs and review some custom code? Unfortunately, these APIs are meant primarily for developers and even with the right skills, using them requires quite some effort. Many applications in Office 365 expose APIs that make it possible to interact with them and automate some tasks. Should you 'get clicking' or is there a better way? Automation for the masses So the meeting is over and you're left with a bunch of action points that you need to put in Planner. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |