![]() 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. |