cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
MMTN
Regular Visitor

Microsoft lists flow for recurring tasks

Dear all,

 

I'm using Microsoft Lists for the management of maintenance tasks.

The list is structured as follows:

 

Title/description of the task, Machine (the machine on which the task should be performed), Iterval (None, Monthly, Annually, ...), State (Scheduled, Completed), Next due date

 

There are 2 types of tasks: one-time tasks (for which the interval is set to None) and recurring tasks (with different possible intervals, mainly monthly and annually).

 

I tried to create a flow that, when the State of a task is changed from Scheduled to Completed it creates a new task with the same information but with an updated Next Due Date (ex. for Monthly I used the function AddDays(utcNow(),30). If the Interval is set to none nothing happens.

 

Do you have some ideas? 

Thank you!

1 ACCEPTED SOLUTION

Accepted Solutions

Hi @MMTN sorry for the delay, I was on a trip this weekend and this was buried in my emails.

 

I made an example for you to reference.

Example Flow OverviewExample Flow Overview

  • This flow will trigger when an item is modified.
  • Current Time - The same as using utcNow() but has a dynamic output instead of using an expression.
  • Get Changes for an Item or File (Properties Only) - This will reference the item that was changed and tell what columns or properties were changed.
  • Condition - Will check if the Inspection Status column was changed and if the Inspection Status column is "Completed"
    • If Yes - it will update the Completion Inspection Date with the Current Time
    • If No - It will Terminate the Flow - basically end the flow from running
  • Switch - Uses the output value of Inspection Interval to determine which case to use
    • Case 1 - Weekly
    • Case 2 - Monthly
    • Case 3 - Yearly
  • Each case uses
    • Add to Time - will add the amount of time to the Current Time output. This is the same as addDays(utcNow(),7) or addDays(utcNow(),30)
    • Create Item - will use the outputs of the initial trigger to create a new item in the list.

 

Below I'm going to show the SharePoint List that I used as an example and the choice columns "Inspection Interval" and "Current Inspection Status" which have the options.

Initial SharePoint List with all items Scheduled and No Items CompletedInitial SharePoint List with all items Scheduled and No Items CompletedSharePoint List Settings to show the column types being usedSharePoint List Settings to show the column types being usedColumn - Inspection Interval - has time options for inspections (One-Time, Weekly, Monthly, Yearly)Column - Inspection Interval - has time options for inspections (One-Time, Weekly, Monthly, Yearly)Column - Current Inspection Status - will have the selection of Scheduled or CompletedColumn - Current Inspection Status - will have the selection of Scheduled or Completed

 

Below are close up of the flow actions:

Flow Detail 1 - Trigger - Current Time - Get Changes For an Item or FileFlow Detail 1 - Trigger - Current Time - Get Changes For an Item or FileFlow Detail 2 - Condition - Update Item - TerminateFlow Detail 2 - Condition - Update Item - Terminate

Zoomed Flow Detail 2 - ConditionZoomed Flow Detail 2 - Condition

Flow Detail 3 - Switch - Case 1- Case 2 - Case 3 - DefaultFlow Detail 3 - Switch - Case 1- Case 2 - Case 3 - DefaultZoomed Flow Detail 3 - Switch Case 1Zoomed Flow Detail 3 - Switch Case 1Zoomed Flow Detail 3 - Switch Case 2Zoomed Flow Detail 3 - Switch Case 2Zoomed Flow Detail 3 - Switch Case 3 and DefaultZoomed Flow Detail 3 - Switch Case 3 and Default

 

Using my initial SharePoint list example, I changed all of the items to a Completed status. This added the time the completed status was changed to the "Completed Inspection Date" column. It also added a new row for each item. 

Note, the new scheduled inspection date is based on the date the previous inspection was completed and the interval. For example, Item 1 - Monthly Label Alignment is a Monthly inspection that was scheduled for October 1, 2023. I changed the inspection status to Completed today on September 26, 2023 at 8:41 AM. 

Since this is a Monthly inspect, the new created Item 6 - has a Scheduled Inspection Date is October 26, 2023 at 8:41 AM.

 

Results of Changing the original items (1-5) status to Completed. The new created items (6-9) from the flow.Results of Changing the original items (1-5) status to Completed. The new created items (6-9) from the flow.

 

 

Hope this helps, let me know if you have any questions,

View solution in original post

12 REPLIES 12

That doesn't seem like a bad method if you are trying to keep an easy record of when tasks are completed. So there will be one row per task completed for each machine. If you filter the list by a machine, you can easily see all of the tasks that were scheduled and completed. 

 

You could even have a Completed date and a calculation to show the difference in days between scheduled date and completed date. This would show if it went over due or earlier than expected.

 

Are you thinking you only want 1 row per machine and continually update that row with the scheduled and completed date? So it is basically showing the last date it was completed and the next date it should be completed?

MMTN
Regular Visitor

Dear @wskinnermctc, thank you for your reply.

I would like that a new row is added so that I can keep track of how many times that task has been performed.

i give you a brief example.

i create a new element in the list as follows:

Check belt wear-MachineXYZ-monthly-Scheduled-21/09/2023

 

on the 19/09 I perform the task (earlier than the actual due date in this example) and I set the task to completed.

it would be wonderful if the completed task remains for tracking purposes and at the same time a new task with the same information but due date for 19/10 is created with Scheduled state is created.

 

I hope I was clear explaining what is my goal with this flow!

I guess I didn't understand if you got your flow to function. I read that as you created a flow that did that, but you wanted to know if there was a different way. Now I see you didn't get it to work and asking how to do it.

 

Tell me the interval choices you use and I can make an example for you to copy.

  • None
  • Weekly???
  • Monthly
  • Yearly

Are these task dates really specific? Like it must be done that day? Want to know in case dates land on weekends or something if I need to try and adjust for that.

Like could it be 30 working days? 30 calendar days? Is it always the 1st of the month? Is a month specific to the next month or just use 30 days?

 

Trying to understand how you need this time calculated. I'll start with just 30 days, and if you respond with something different we can adjust.

MMTN
Regular Visitor

MMTN_0-1695190124392.png

This is the flow that I have built. It seems to works, almost. It creates a new element with the information I need and the exact due date but it also create a simple copy of the element.

I don't understand why it creates 2 elements when I just asked it to create one!

 

Regarding your questions:

The interval choices could be 3 or 4, I will need to see according to the actual requirements of the machines:

  • weekly
  • monthly
  • yearly

could be a good starting point.

The task are not specific, in fact it's just an indication of the date in which they should be performed (especially for monthly and yearly ones).. maybe the due date is set to, for example, the 27/09 but the task could be performed on the 25/09 or 29/09.

I think that i need just an addition of 7, 28, 364 days (so that the new due date will be always on the same day, in this case I think that addDays function is enough).

 

Thank you very much for your time.

Dear @wskinnermctc, could you please take a look at my latest reply? I forgot to tag you!

Thank you!

Hi @MMTN sorry for the delay, I was on a trip this weekend and this was buried in my emails.

 

I made an example for you to reference.

Example Flow OverviewExample Flow Overview

  • This flow will trigger when an item is modified.
  • Current Time - The same as using utcNow() but has a dynamic output instead of using an expression.
  • Get Changes for an Item or File (Properties Only) - This will reference the item that was changed and tell what columns or properties were changed.
  • Condition - Will check if the Inspection Status column was changed and if the Inspection Status column is "Completed"
    • If Yes - it will update the Completion Inspection Date with the Current Time
    • If No - It will Terminate the Flow - basically end the flow from running
  • Switch - Uses the output value of Inspection Interval to determine which case to use
    • Case 1 - Weekly
    • Case 2 - Monthly
    • Case 3 - Yearly
  • Each case uses
    • Add to Time - will add the amount of time to the Current Time output. This is the same as addDays(utcNow(),7) or addDays(utcNow(),30)
    • Create Item - will use the outputs of the initial trigger to create a new item in the list.

 

Below I'm going to show the SharePoint List that I used as an example and the choice columns "Inspection Interval" and "Current Inspection Status" which have the options.

Initial SharePoint List with all items Scheduled and No Items CompletedInitial SharePoint List with all items Scheduled and No Items CompletedSharePoint List Settings to show the column types being usedSharePoint List Settings to show the column types being usedColumn - Inspection Interval - has time options for inspections (One-Time, Weekly, Monthly, Yearly)Column - Inspection Interval - has time options for inspections (One-Time, Weekly, Monthly, Yearly)Column - Current Inspection Status - will have the selection of Scheduled or CompletedColumn - Current Inspection Status - will have the selection of Scheduled or Completed

 

Below are close up of the flow actions:

Flow Detail 1 - Trigger - Current Time - Get Changes For an Item or FileFlow Detail 1 - Trigger - Current Time - Get Changes For an Item or FileFlow Detail 2 - Condition - Update Item - TerminateFlow Detail 2 - Condition - Update Item - Terminate

Zoomed Flow Detail 2 - ConditionZoomed Flow Detail 2 - Condition

Flow Detail 3 - Switch - Case 1- Case 2 - Case 3 - DefaultFlow Detail 3 - Switch - Case 1- Case 2 - Case 3 - DefaultZoomed Flow Detail 3 - Switch Case 1Zoomed Flow Detail 3 - Switch Case 1Zoomed Flow Detail 3 - Switch Case 2Zoomed Flow Detail 3 - Switch Case 2Zoomed Flow Detail 3 - Switch Case 3 and DefaultZoomed Flow Detail 3 - Switch Case 3 and Default

 

Using my initial SharePoint list example, I changed all of the items to a Completed status. This added the time the completed status was changed to the "Completed Inspection Date" column. It also added a new row for each item. 

Note, the new scheduled inspection date is based on the date the previous inspection was completed and the interval. For example, Item 1 - Monthly Label Alignment is a Monthly inspection that was scheduled for October 1, 2023. I changed the inspection status to Completed today on September 26, 2023 at 8:41 AM. 

Since this is a Monthly inspect, the new created Item 6 - has a Scheduled Inspection Date is October 26, 2023 at 8:41 AM.

 

Results of Changing the original items (1-5) status to Completed. The new created items (6-9) from the flow.Results of Changing the original items (1-5) status to Completed. The new created items (6-9) from the flow.

 

 

Hope this helps, let me know if you have any questions,

Dear @wskinnermctc that's exactly what I was looking for. Thank you very much!

@wskinnermctc 

I came across this thread and thanks for ur detailed reply!

As for myself, I have tried to copy this flow but sadly it doesn't work.

When I try to test my flow, it gets stuck at the first item "when an item or file gets modified". (stuck for hours - in progress"

 

Because i'm a beginner to Flows, it might be a user error from my side.

I have placed all my items marked as "completed" and all date colums are empty.

We are working with daily tasks so I made the "Case 1" interval on the switch part to 1 day interval instead. 

 

Since i'm not able to test yet, from what I understand now is that there will be a new line created to see progress of previous line. 

As i'm working with daily tasks, it will clean itself or will it keep adding lines daily? 

 

Thanks in advance for taking time to answer.

 

Best regards

Hi @TORFS_BE this example will create a new line. So I don't know exactly what you mean by "clean itself" each day.

 

It is strange that your flow is getting stuck at the trigger/first action.

 

I think you should create a new post on the forum. Explain what you are trying to accomplish and give some screenshots of your sharepoint list and current flow. You can also add a link to this post and say that you were following these examples.

 

I say to create a new post because other people will look at it and it will get solved faster.

Hi Wskinnermctc,

 

I have tried to reproduce your example, unfortunately, one of the first differences I see when carrying it out, is that when introducing the "get changes for an element or file" block when entering the ID the system introduces everything in a for each state.

I think the problem is with the Trigger settings. You need to turn "Split On" to the On.

If it is turned off, it creates an Apply to Each.

 

  • Delete the trigger you have
  • Add the same trigger back to the flow as the new trigger
  • Go to the Settings of the trigger
  • Split On - turn to On
  • Then try your steps and see if the apply to each is removed.

 

wskinnermctc_0-1706022409716.png

 

wskinnermctc_1-1706022436245.png

 

 

That was the point!! now it works, thank you very much for your help!! 😊

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!

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.    

Summer of Solutions | Week 3 Results | Win free tickets to the Power Platform Conference

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  

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 (4,794)