![]() ![]() ![]() The two tables are created using the same action, from is the body from the filter array actions and I've included headings and columns are Custom. I add the final scope to create the email. ![]() In order to create the email I will convert the two filtered arrays into html tables and then add headings before each table. The formula is utcNow()),less(item()?, addDays(utcNow(), 7))) So add the Filter Array action and click Edit in advanced mode. This will require the filter to edited in advanced mode. The scond filter array needs the Finish date to be greater than or equal to today and less than today plus 7 days. The first filter is a simple one of the finish date being less than today so can done using the simple editor. In the email I want to lists of tasks, late ones and upcoming ones, so we do two filter arrays. Then I expand the Advanced options to add an OData filter which is: IsSummary eq false and PercentComplete lt 100 I add List Tasks from the Project Online connector and use the output from the Compose action I start by adding a new Scope action and rename it to Get Task Lists. This means that in the List Tasks action we can use an OData filter to not include them. So this will not include Summary tasks and tasks that have been completed. Then I am ready to use that Id to get a list of tasks.įor this post I want to list Late tasks and tasks due in the next 7 days. Then I run the flow to check that the compose action does return a project id. So I add a compose action and click on expression and add the following first(body('Filter_array'))? Then we use a compose action to get the Id field from the first row in the filtered array. So before the List Tasks action can be added, I add a scope to the flow and add a List Projects action and then add a Filter Array action to filter it down to the Returned projects Project Name equalling "Training Plan". List projects action does not include an advanced features so we need to use a Filter Array action. We know the project name so we can fetch the list of projects and then use the name to filter the returned array. Unlike some other actions in flow when you enter the URL you do not get a drop down of the available projects, we need to get project id first. This action requires 2 parameters, URL of the project site and the Project ID. The Project Online connection includes an action of List Tasks. Using the same structure Flow will be split into three scopes. This post is split into 3 parts, getting Project ID, Listing the tasks and Sending the email. The trigger for this example will be a scheduled trigger once a week on a Monday morning. This post will work fetching the late and upcoming tasks for one project and then creating the email to send. Flow includes a list of actions for Project Online which include getting a list of projects and getting a list of tasks. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |