cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
Anonymous
Not applicable

Create A Task based on date

Hi Everyone,

 

I am new to Microsoft flows and forms. I am trying to create a Task in the planner based on the  deadline of submission of the project( is filed in forms)

 

When the user fills the forms I have one variable which asks for when the deadline of the project.

based on the deadline date   I Have to create A task in the planner which should be completed before 10 days actual deadline date 

 

but  I am not able create a task when the user not having 10 days deadline ( which means the user feed information in form and his project complete in 5 days) How slove this problem?  

1 ACCEPTED SOLUTION

Accepted Solutions

@Anonymous Ok, I think I've got it sorted out.  Here's what I heard:

  • If the difference between the Project Due Date and today is 7 or more, the Task Due Date will be 2 days less.

  • If the difference is 2-6 days out, then it will be 1 day less.

  • Any sooner, and the Task Due Date will be the same as the Project Due Date.

I've made a flow chart here:20190620a.PNG

There's a bunch going on here (for the beginner) and my usual caveat is that there are probably more elegant ways to do this, but these are the tools I know how to use.

  1. The first thing we want to do is get everything in the same timezone.  Since all of the backend math is going to be in UTC, we want to convert the due date from the form to that.  (I used a manual trigger since it seemed like the trigger part of your Flow was working fine.  You'll want to change the Source Time Zone in the second box to your local timezone.
    20190620b.PNG

  2. We want to set up variables to hold the dates in a special format called "ticks".  This is what Flow (and a lot of other things, apparently) use to do math with dates.  Here, I've initialized a variable for today, the due date, and the difference (all Integer), and then one we'll use as the Task Due Date (string).
    20190620c.PNG

  3. For the UTC value, I used an expression that counts the number of 'ticks' for right now, and then divided that by the number of ticks in a day:  "DIV(ticks(utcNow()),864000000000)" (without the quotes).  For the Due Date ticks, I used "DIV(ticks(body('Convert_Due_Date_to_UTC')) ,864000000000)" where 'Convert_Due_Date_to_UTC' is the dynamic output of Step 1.
  4. To get the difference between the two (DateDiff), I used "sub(variables('varTicksDue'),variables('varUTCNowTicks'))" which subtracts one variable from another.
  5. Finally, I set the default of TaskDueDate to the converted Project Due Date.  That may change later depending on the math.
  6. Next, we want to adjust the TaskDueDate based on what the DateDiff is, right?  We do this with conditions.  There are other ways to do this, but I nested the conditions because I wanted different results based on the input.  Conditions let you ask a question, and then choose a path if the answer is "Yes" and a different path if the answer is "No".  The first question I asked was if the DateDiff was 7 days or more.
  7. If the answer was yes, I want to remove two days from the Project Due Date and make that my TaskDueDate.  You can do this with the "Subtract from Time" action and then the "Set Variable" action:
    20190620d.PNG

     

  8. If the answer is "No" (meaning the Project due date is less than 7 days out), then I want to ask another question to see if it is within 2 days.  That means your "No" path will have another condition inside it like this:
    20190620g.PNG

     

  9. If the answer to "Is it less than two days out" is Yes, we want the TaskDueDate to stay as the default (Project Due Date), so the "Yes" path can actually stay blank.  On the "No" path, we want to use the same method as Step 7 to remove one day and update the TaskDueDate variable.
  10. Last, we get to create the task.  But before we do that, we want to format the date/time to what Planner is expecting.  I use Convert Timezone for this, but there are other ways.  Not the upper/lower casing on the format...that does matter.
    20190620e.PNG

     

    And then the create task:20190620f.PNG

I hope that helps.  I did a more thorough write up here, but I think this one covers your scenario.  Keep us posted.

 

Thanks!

-Ed-

 

 

 

If this reply has answered your question or resolved your challenge, please consider marking it as a Solution. This helps other users find it more easily via search.

 

View solution in original post

9 REPLIES 9
edgonzales
Most Valuable Professional
Most Valuable Professional

@Anonymous 

Hi there!  So, this one was fun since I haven't ever used these functions before and they were behaving....'oddly'.  You can totally do this with an expression, but I don't know the exact syntax and I thought this was more fun.

 

In between getting your date (in the form) and adding the task in Planner, add two steps:

 

First is "Subtract from Time" - This one is pretty self-explanatory in the steps, but I had no idea it existed:20190618a.PNG

That step will back up 10 days and generate a date, but it also includes the time, which messes things up on the Create Task Step.  Again, you can do all of this with an expression, but this is the hammer I have:20190618b.PNG

Note the Format String.  The case of the letters does matter, and I thought it was weird that I had to switch like that...but it worked.  Essentially, we're taking the input date/time, keeping the same timezone, and spitting out the same time in a new format that only includes the date.  Feel free to adjust the Destination TimeZone, but I think Planner might do that already for you.20190618c.PNG

On the Create Task site, you can grab everything else from the Form and just add the "Converted Time" as your Due Date.  Should work splendidly.  

 

Keep us posted, though.

-Ed-

 

 

If this reply has answered your question or resolved your challenge, please consider marking it as a Solution. This helps other users find it more easily via search.

Anonymous
Not applicable

@edgonzales  I have created a task if there no 10 days gap for the deadline, for example, a student fill form today and his deadline after 3 days, in this case, I getting error message task is not create how to solve this problem if student has not have 10 days gap for deadline 

Ah, that makes sense.  We'd have to set a condition to check for that.  What would your (Pre-Flow) process be when this happens?

 

-Ed-

Anonymous
Not applicable

@edgonzales  I Would like to set the pre-flow process both to create a task.

 

Condition 1: if it has 10  days map create a task with the given date.

 

Condition 2: if it does not have 10  days also create a task-based deadline before on the same deadline day with or 2 days before the deadline.  

ok, and just poking the box a bit:  What if the deadline is inside that one day? 

What I meant with the "Pre-Flow" part was what did this process look like before you started automating?  Like xRM solutions, Flow is a great way to automate existing processes and when we're building brand new processes (in Flow, or out), it's a good idea to sketch out the steps and consider what to do when something falls "outside of the machine".

 

I'll start building something now using some conditions and we'll see how that looks.

Anonymous
Not applicable

if the deadline is inside that one day means to create the task and have a task deadline on the same day.

Anonymous
Not applicable

@edgonzales if the deadline is inside that one day means to create the task and have a task deadline on the same day.

v-lin-msft
Post Prodigy
Post Prodigy

Hi @Anonymous,

 

I feel confused that why cannot create a task have no 10 days gap for deadline.

You said that I getting error message task is not create how to solve this problem if student has not have 10 days gap for deadline. Could you share us the wrong message?

This is my flow configuration that get detail from the MS Form, then get the detail and create a task in my plan, you can refer to it:

Annotation 2019-06-21 143105.png

Annotation 2019-06-21 143047.png

 

 

 

You said that when a student submits a task with a deadline of more than ten days, I guess your purpose should be to send an email to remind the student to complete the task ten days before the deadline. However, if the completion date of student submission is within ten days, there is no way to send the reminder email of ten days ago. Then you can set a reminder email of two days or one day ago. This is another flow I built based on my guess of your purpose:

 

Step1: Create an action Recurrence, the flow will trigger every day, then get the list of tasks.

Annotation 2019-06-21 144319.png

Step2: Add a condition that if Due Date time is equal to 10 days or 2 days or 1 day later:

If yes, send remind email.

(Please convert the format of UtcNow() date).

Annotation 2019-06-21 144707.png

I hope it can help you. If you still have questions, please contact us.

 

Best Regards,

Community Support Team _ Lin Tu

If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

 

@Anonymous Ok, I think I've got it sorted out.  Here's what I heard:

  • If the difference between the Project Due Date and today is 7 or more, the Task Due Date will be 2 days less.

  • If the difference is 2-6 days out, then it will be 1 day less.

  • Any sooner, and the Task Due Date will be the same as the Project Due Date.

I've made a flow chart here:20190620a.PNG

There's a bunch going on here (for the beginner) and my usual caveat is that there are probably more elegant ways to do this, but these are the tools I know how to use.

  1. The first thing we want to do is get everything in the same timezone.  Since all of the backend math is going to be in UTC, we want to convert the due date from the form to that.  (I used a manual trigger since it seemed like the trigger part of your Flow was working fine.  You'll want to change the Source Time Zone in the second box to your local timezone.
    20190620b.PNG

  2. We want to set up variables to hold the dates in a special format called "ticks".  This is what Flow (and a lot of other things, apparently) use to do math with dates.  Here, I've initialized a variable for today, the due date, and the difference (all Integer), and then one we'll use as the Task Due Date (string).
    20190620c.PNG

  3. For the UTC value, I used an expression that counts the number of 'ticks' for right now, and then divided that by the number of ticks in a day:  "DIV(ticks(utcNow()),864000000000)" (without the quotes).  For the Due Date ticks, I used "DIV(ticks(body('Convert_Due_Date_to_UTC')) ,864000000000)" where 'Convert_Due_Date_to_UTC' is the dynamic output of Step 1.
  4. To get the difference between the two (DateDiff), I used "sub(variables('varTicksDue'),variables('varUTCNowTicks'))" which subtracts one variable from another.
  5. Finally, I set the default of TaskDueDate to the converted Project Due Date.  That may change later depending on the math.
  6. Next, we want to adjust the TaskDueDate based on what the DateDiff is, right?  We do this with conditions.  There are other ways to do this, but I nested the conditions because I wanted different results based on the input.  Conditions let you ask a question, and then choose a path if the answer is "Yes" and a different path if the answer is "No".  The first question I asked was if the DateDiff was 7 days or more.
  7. If the answer was yes, I want to remove two days from the Project Due Date and make that my TaskDueDate.  You can do this with the "Subtract from Time" action and then the "Set Variable" action:
    20190620d.PNG

     

  8. If the answer is "No" (meaning the Project due date is less than 7 days out), then I want to ask another question to see if it is within 2 days.  That means your "No" path will have another condition inside it like this:
    20190620g.PNG

     

  9. If the answer to "Is it less than two days out" is Yes, we want the TaskDueDate to stay as the default (Project Due Date), so the "Yes" path can actually stay blank.  On the "No" path, we want to use the same method as Step 7 to remove one day and update the TaskDueDate variable.
  10. Last, we get to create the task.  But before we do that, we want to format the date/time to what Planner is expecting.  I use Convert Timezone for this, but there are other ways.  Not the upper/lower casing on the format...that does matter.
    20190620e.PNG

     

    And then the create task:20190620f.PNG

I hope that helps.  I did a more thorough write up here, but I think this one covers your scenario.  Keep us posted.

 

Thanks!

-Ed-

 

 

 

If this reply has answered your question or resolved your challenge, please consider marking it as a Solution. This helps other users find it more easily via search.

 

Helpful resources

Announcements

Community will be READ ONLY July 16th, 5p PDT -July 22nd

Dear Community Members,   We'd like to let you know of an upcoming change to the community platform: starting July 16th, the platform will transition to a READ ONLY mode until July 22nd.   During this period, members will not be able to Kudo, Comment, or Reply to any posts.   On July 22nd, please be on the lookout for a message sent to the email address registered on your community profile. This email is crucial as it will contain your unique code and link to register for the new platform encompassing all of the communities.   What to Expect in the New Community: A more unified experience where all products, including Power Apps, Power Automate, Copilot Studio, and Power Pages, will be accessible from one community.Community Blogs that you can syndicate and link to for automatic updates. We appreciate your understanding and cooperation during this transition. Stay tuned for the exciting new features and a seamless community experience ahead!

Summer of Solutions | Week 4 Results | Winners will be posted on July 24th

We are excited to announce the Summer of Solutions Challenge!    This challenge is kicking off on Monday, June 17th and will run for (4) weeks.  The challenge is open to all Power Platform (Power Apps, Power Automate, Copilot Studio & Power Pages) community members. We invite you to participate in a quest to provide solutions to as many questions as you can. Answers can be provided in all the communities.    Entry Period: This Challenge will consist of four weekly Entry Periods as follows (each an “Entry Period”)   - 12:00 a.m. PT on June 17, 2024 – 11:59 p.m. PT on June 23, 2024 - 12:00 a.m. PT on June 24, 2024 – 11:59 p.m. PT on June 30, 2024 - 12:00 a.m. PT on July 1, 2024 – 11:59 p.m. PT on July 7, 2024 - 12:00 a.m. PT on July 8, 2024 – 11:59 p.m. PT on July 14, 2024   Entries will be eligible for the Entry Period in which they are received and will not carryover to subsequent weekly entry periods.  You must enter into each weekly Entry Period separately.   How to Enter: We invite you to participate in a quest to provide "Accepted Solutions" to as many questions as you can. Answers can be provided in all the communities. Users must provide a solution which can be an “Accepted Solution” in the Forums in all of the communities and there are no limits to the number of “Accepted Solutions” that a member can provide for entries in this challenge, but each entry must be substantially unique and different.    Winner Selection and Prizes: At the end of each week, we will list the top ten (10) Community users which will consist of: 5 Community Members & 5 Super Users and they will advance to the final drawing. We will post each week in the News & Announcements the top 10 Solution providers.  At the end of the challenge, we will add all of the top 10 weekly names and enter them into a random drawing.  Then we will randomly select ten (10) winners (5 Community Members & 5 Super Users) from among all eligible entrants received across all weekly Entry Periods to receive the prize listed below. If a winner declines, we will draw again at random for the next winner.  A user will only be able to win once overall. If they are drawn multiple times, another user will be drawn at random.  Individuals will be contacted before the announcement with the opportunity to claim or deny the prize.  Once all of the winners have been notified, we will post in the News & Announcements of each community with the list of winners.   Each winner will receive one (1) Pass to the Power Platform Conference in Las Vegas, Sep. 18-20, 2024 ($1800 value). NOTE: Prize is for conference attendance only and any other costs such as airfare, lodging, transportation, and food are the sole responsibility of the winner. Tickets are not transferable to any other party or to next year’s event.   ** PLEASE SEE THE ATTACHED RULES for this CHALLENGE**   Week 1 Results: Congratulations to the Week 1 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge.   Community MembersNumber SolutionsSuper UsersNumber Solutions Deenuji 9 @NathanAlvares24  17 @Anil_g  7 @ManishSolanki  13 @eetuRobo  5 @David_MA  10 @VishnuReddy1997  5 @SpongYe  9JhonatanOB19932 (tie) @Nived_Nambiar  8 @maltie  2 (tie)   @PA-Noob  2 (tie)   @LukeMcG  2 (tie)   @tgut03  2 (tie)       Week 2 Results: Congratulations to the Week 2 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Week 2: Community MembersSolutionsSuper UsersSolutionsPower Automate  @Deenuji  12@ManishSolanki 19 @Anil_g  10 @NathanAlvares24  17 @VishnuReddy1997  6 @Expiscornovus  10 @Tjan  5 @Nived_Nambiar  10 @eetuRobo  3 @SudeepGhatakNZ 8     Week 3 Results: Congratulations to the Week 3 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Week 3:Community MembersSolutionsSuper UsersSolutionsPower Automate Deenuji32ManishSolanki55VishnuReddy199724NathanAlvares2444Anil_g22SudeepGhatakNZ40eetuRobo18Nived_Nambiar28Tjan8David_MA22   Week 4 Results: Congratulations to the Week 4 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Week 4:Community MembersSolutionsSuper UsersSolutionsPower Automate Deenuji11FLMike31Sayan11ManishSolanki16VishnuReddy199710creativeopinion14Akshansh-Sharma3SudeepGhatakNZ7claudiovc2CFernandes5 misc2Nived_Nambiar5 Usernametwice232rzaneti5 eetuRobo2   Anil_g2   SharonS2  

Check Out | 2024 Release Wave 2 Plans for Microsoft Dynamics 365 and Microsoft Power Platform

On July 16, 2024, we published the 2024 release wave 2 plans for Microsoft Dynamics 365 and Microsoft Power Platform. These plans are a compilation of the new capabilities planned to be released between October 2024 to March 2025. This release introduces a wealth of new features designed to enhance customer understanding and improve overall user experience, showcasing our dedication to driving digital transformation for our customers and partners.    The upcoming wave is centered around utilizing advanced AI and Microsoft Copilot technologies to enhance user productivity and streamline operations across diverse business applications. These enhancements include intelligent automation, AI-powered insights, and immersive user experiences that are designed to break down barriers between data, insights, and individuals. Watch a summary of the release highlights.    Discover the latest features that empower organizations to operate more efficiently and adaptively. From AI-driven sales insights and customer service enhancements to predictive analytics in supply chain management and autonomous financial processes, the new capabilities enable businesses to proactively address challenges and capitalize on opportunities.    

Updates to Transitions in the Power Platform Communities

We're embarking on a journey to enhance your experience by transitioning to a new community platform. Our team has been diligently working to create a fresh community site, leveraging the very Dynamics 365 and Power Platform tools our community advocates for.  We started this journey with transitioning Copilot Studio forums and blogs in June. The move marks the beginning of a new chapter, and we're eager for you to be a part of it. The rest of the Power Platform product sites will be moving over this summer.   Stay tuned for more updates as we get closer to the launch. We can't wait to welcome you to our new community space, designed with you in mind. Let's connect, learn, and grow together.   Here's to new beginnings and endless possibilities!   If you have any questions, observations or concerns throughout this process please go to https://aka.ms/PPCommSupport.   To stay up to date on the latest details of this migration and other important Community updates subscribe to our News and Announcements forums: Copilot Studio, Power Apps, Power Automate, Power Pages

Users online (879)