@Anonymous my example of how to create the flow is shown below. The SharePoint list is as follows:
1. In the flow (I've used the new designer although still prefer the classic!) the trigger is when an item or a file is modified. I've then added a compose action to get the current due date.
2. Next, add a Get changes for an item or a file (properties only) action. Select the ID from the dynamic content box and for the Since field select Trigger Window Start Token.
3. Add a condition which should be Has Column Changed Status is equal to true AND Status Value is equal to Completed. It's Status Value because Status is a choice column. You need both criteria for the condition to prevent infinite loops.
4. You can leave the red if no channel empty. In the green if yes channel add a switch control that is a type of condition that looks at 1 thing and then can have up to 25 "cases". So case frequency is monthly do these actions. Case frequency is annually do these actions.
5. Rename the first case to Case Annually, add an add to time action and set it to add 12 months to the outputs of the compose you added at the top of the flow.
6. Still inside the green if yes channel add an update item action, select ID from the dynamic content box, select calculated time from the dynamic content box for the Due field, and select Open from the dropdown for the Status Value field.
7. We'll change Barbados in our list to Completed:
8. Initially, until the flow completes that will change the Barbados item to look like this:
9. But once the flow has run it updates Barbados with new due date in 1 month and changed the status back to open. I've also changed Guadaloupe and you can see it's added 12 months to the due column and changed the status to open.
Rob
Los Gallardos
If I've answered your question or solved your problem, please mark this question as answered. This helps others who have the same question find a solution quickly via the forum search. If you liked my response, please consider giving it a thumbs up. Thanks.
