Hello,
I have a sharepoint library that has a review date and three other calculated columns for 30 days prior, 60 days prior and 90ty days prior. When the 30 day, 60 day and 90 day equals today I want the folow to send the reminder email
However I keep getting the following error which I know is because of the 28 day limit on flows. How do I work around that?
"The provided 'Wait' action 'until' value '10/7/2020 5:00:00 AM' (UTC) is not supported for the 'Consumption' SKU. The maximum wait duration supported for this SKU is '30' day(s)".
Here is my flow screen shot.
Solved! Go to Solution.
Hi All,
After a long night of searching I figured out how to do this. I hope this help someone else avoid the issue and errors I had.
The requirements where:
Documents in a SharePoint library have an assigned due date.
30days prior to that due date send a reminder to the Owner of the document.
60days prior to that due date send a reminder to the Owner of the document.
90days prior to that due date send a reminder to the Owner of the document.
CONFIGURATION: There is three calculated columns added to the library to calculate out the 30 days prior, 60 days prior and 90 days prior to due date. There is one flow for each reminder email.The recurrence is scheduled for 8 am. The workflow then reviews the dates in the 30 day, 60 day and 90 day columns. If any of the dates match today then the email reminder is sent.
Note: Text noted with {{example}} are selected via the dynamic list.
Here are the Steps.
If Yes Select Action Apply to Each {{Owned By}}. Ensures the next steps are applied to each Owner listed on the item in the SharePoint library. (I had mutiple owners)
I hope this helps anyone else avoid the same issues and errors as I had.
Enjoy!
Mel
I hope this helps anyone else avoid the same issues and errors as I had.
Enjoy!
Mel
8. Select Action Send email. This is the email template used to send the reminder.
9. After you save the flow you can copy it to make one for the 60 days and 90 days. I named my flows as such 30 Day Reminder, 60 Day Reminder and 90 Day Reminder.
When Done it should look like this.
Hello @Anonymous
Please try and follow a structure like this:
Basically, you want to have the flow run daily, and have multiple branches for each type of reminder.
In my example Dynamics365 is being used but you can change this to SharePoint, and use a filter for checking if the outputs for current date+X amount of days is equal to your Review date
Proud to be a Flownaut!
hi @Anonymous you can use an action to wait more that 30 days. You can follow @Jcook example to made this. What you can do is addDays and use a condition to compare.
Proud to be a Flownaut!
Hi Jcook,
Let me try that and see how it goes.
Thank you,
Mel
Hi,
How did you set the filter? I keep getting this error. The expression "Review Due Date eq 2020-10-06" is not valid.
Thank you,
Melody
@Anonymous
Try:
Review Due Date eq '2020-10-06'
Proud to be a Flownaut!
I tried that with no luck.
Mel
@Anonymous
Can you add a Compose action before your Condition and input Review Due Date.
Than run flow. Basically to see what the format of the date is.
Proud to be a Flownaut!
@Anonymous
Ahhh, I can see in your original post your format is MM/dd/yyyy but you are comparing it with date format of yyyy-MM-dd
Use a convert timezone on that date as well, so you can match them
Proud to be a Flownaut!
Hi,
None of these options worked. I continue to get the same error when using the filter query option. "Column 'ReviewDate' does not exist. It may have been deleted by another user". It hasn't been deleted. I even created a second column same results.
Does anyone have the steps to complete a flow like this? Here are the basic requirements.
The requirements are:
Documents in a SharePoint library have an assigned due date.
30days prior to that due date send a reminder to the Owner of the document.
60days prior to that due date send a reminder to the Owner of the document.
90days prior to that due date send a reminder to the Owner of the document.
Do not send a reminder if Item has an approved date.
Hi All,
After a long night of searching I figured out how to do this. I hope this help someone else avoid the issue and errors I had.
The requirements where:
Documents in a SharePoint library have an assigned due date.
30days prior to that due date send a reminder to the Owner of the document.
60days prior to that due date send a reminder to the Owner of the document.
90days prior to that due date send a reminder to the Owner of the document.
CONFIGURATION: There is three calculated columns added to the library to calculate out the 30 days prior, 60 days prior and 90 days prior to due date. There is one flow for each reminder email.The recurrence is scheduled for 8 am. The workflow then reviews the dates in the 30 day, 60 day and 90 day columns. If any of the dates match today then the email reminder is sent.
Note: Text noted with {{example}} are selected via the dynamic list.
Here are the Steps.
If Yes Select Action Apply to Each {{Owned By}}. Ensures the next steps are applied to each Owner listed on the item in the SharePoint library. (I had mutiple owners)
I hope this helps anyone else avoid the same issues and errors as I had.
Enjoy!
Mel
I hope this helps anyone else avoid the same issues and errors as I had.
Enjoy!
Mel
8. Select Action Send email. This is the email template used to send the reminder.
9. After you save the flow you can copy it to make one for the 60 days and 90 days. I named my flows as such 30 Day Reminder, 60 Day Reminder and 90 Day Reminder.
When Done it should look like this.
The first Microsoft-sponsored Power Platform Conference is coming in September. 100+ speakers, 150+ sessions, and what's new and next for Power Platform.
Announcing a new way to share your feedback with the Power Automate Team.
Power Platform release plan for the 2022 release wave 2 describes all new features releasing from October 2022 through March 2023.
Learn to digitize and optimize business processes and connect all your applications to share data in real time.
User | Count |
---|---|
67 | |
27 | |
22 | |
16 | |
13 |
User | Count |
---|---|
129 | |
47 | |
44 | |
34 | |
31 |