Question: What would be a good way to configure conditions that will pull out the matching date and disregard others, so I can then send it in an email alert?
I'd do this as follows:
Optionally - you can also add a column to the list allowing you to record the last time an alert was sent and then use this in your view logic to determine when to show items in the view
If I have answered your question, please mark your post as Solved.
If you like my response, please give it a Thumbs Up.
Thank you @Jay-Encodian for the reminder on using Views.
That's helpful to narrow down the input, but the extra challenge is that those dates could be subject to change, and I'd prefer not introducing more columns that add to the complexity.
Looking at what can be done with the Condition part, I'm not finding clear documentation on the behavior, so at I'm the stage of testing the difference between the following scenarios. I'm guessing that I need to introduce a variable in order to capture the matching date's column and relay it to the email being sent out.
I'm still early on this Flow journey so I'll appreciate any feedback.
I was expecting that the data would change... personally I think you should still to do this by filtering the data in SharePoint and then bringing the data into Flow. The suggestion for an additional column was to record when you had sent an alert for a particular item, whether you filter in the SharePoint view or using Flow conditions... that would apply to both if you chose to records alert activity in this way.
It's akin to building a client / server application... you should query for the smallest data set possible and then process that data as opposed to bringing a large data set back and filtering on the client.
Yes I'm definitely trying to keep in mind the 'smallest data set' best practice.
In our context there's no need to keep track of sent alerts at this level, as the outgoing email from Flow will go out to a ticketing system.
My main challenge is figuring out a reliable way to check daily for a date that's 'X number of days from today' from this SharePoint list of items that can have up to 4 dates that will change over time.
Can you provide some context to these deadlines... it doesn't make a whole of sense... the deadlines must mean something, noting that some deadlines are blank.
Understanding what the date is, how it will be updated, what views needs to be constructed will enable us (the community) to help.
Yes, let me try to explain this scenario better.
* Each item is something like a lease
* Each lease can have from 1 to 4 renewal options (hence some blank fields) that are manually updated over time when an option is exercised, replaced or just expires.
From this I'm looking to set up a daily flow that will:
1. Check those 4 columns for a date that falls withing a certain range - 6 months / 180 days for example -
2. So it can send an email template that says something like "Lease X has a renewal option that will reach its deadline 6 months from today"
At this stage, I don't necessarily need to differentiate which column the matching date is in, as the email includes other details with a link to the item in the SharePoint list.
I hope this is a better explanation.
Handling these 4 columns is what's confusing me, as I have other working Flows that pull from 1 date column using:
Dive into the Power Platform stack with hands-on sessions and labs, virtually delivered to you by experts and community leaders.
Watch Nick Doelman's session from the 2020 Power Platform Community Conference on demand!
Check out the community blog page where you can find valuable learning material from community and product team members!