Jul 20 2019 06:46 AM
Jul 20 2019 09:20 AM
@vperez How are you defining the due date? Planner doesn't have a default, tasks would exist without a date unless you use a formula to add one.
Jul 20 2019 12:59 PM
Jul 21 2019 03:51 AM
@vperez, Flow doesn't have a dynamic field out of the box to populate an Outlook task due date as a Planner task Due date as far as I know. Do you have a fixed time-frame for due dates on tasks? For example, once flagged does every task have a due date 1 week from now? If so you could write a formula in the Flow to insert that date in dynamically with the formula below in the deadline field (this one adds 7 days from today and doesn't set a time):
If not, and you need to manually assign due dates to each task, it may be better to have another Flow running to trigger on a planner task being modified in your Plan, and if the due date is modified it then send out the notification email to your assignee's?
Jul 22 2019 06:31 AM
@ChrisElsdonHi Chris, that is exactly what I have been trying to do. I've included a snip of the flow I am working on . You will see that it has parallel branches only because I have to show my workload to upper management and also have the tasks managed with the salespeople I support.
On the right branch, you will see the email notification at the bottom I added which does goes through with the Title of the task however the Due Date does not and I do not understand why the Title goes through but the manually assigned due date does not, it's very frustrating.
Jul 22 2019 01:59 PM
@vperezwhich step in that right hand flow are you assigning the due date?
Jul 22 2019 02:07 PM
@ChrisElsdonI enter the due date after the 'Update task details 2' but before I assign it to myself 'When a task is assigned to me' as that triggers the email to be sent.
Jul 24 2019 12:56 AM
@vperezI did some testing on my tenant, and when re-creating your flow I am also unable to get the Due Date to write into an email. It seems that although the Due Date is picked up by the Flow it is not able to be written into the email.
But when I put the section of your flow that triggers on when a task is assigned to you in a totally seperate flow its works. As the Trigger is a task assigned to me (in any Plan) I do not think that there is any harm in moving it to a seperate Flow here. I'm not sure why its not working in the single Flow you have and maybe some better minds than mine can help you out here, or you can raise a support ticket to Microsoft to investigate properly.
Hope that helps.