Answered

Email reminder for multiple expiry columns

(0) Share

Report

Posted on by Steve-O28

Hi all,

I am attempting to build a flow to send reminder emails from a specific email address to a specific email address 30 before expiry date.

I have numbered pouches that contain multiple products - each pouch contains the same 8 products with a variety of different expiry dates.

So the expiry date for product A in pouch 1 might be different to the expiry date for product A in pouch 5.

I have a SharePoint list that is set up as follows:

My first column is the pouch number I.e. 1, 2, 3, 4 etc and each subsequent column is the product name I.e. Cheese, Bread, Milk. The expiry dates are then filled into the appropriate box.

I wish to send an email to a specific email address from a specific email address 30 days before a product is due to expire. I wish the email to say something like:

“Cheese is due to expire in 30 days in the following pouches:

Bread is due to expire in 30 days in the following pouches:

Milk is due….. etc”

Here is an image of an example list setup the same as my list

thanks for your assistance

Categories:

Building flows

I have the same question (0)

All responses (7)

Answers (1)

Sort by

David_MA 14,393 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!
If I accurately understand what you want to do, this is not too complicated. You will use the following actions three times to get each of your product types, and then combine the results into your e-mail:
Get items
Condition
Select
Create HTML Table
At a high level, your workflow will look like this:
Then initialize a variable named "Expiration", which is a string with the expression addDays(utcNow(),30,'yyyy-MM-dd').
You will then use this variable in each get items action to filter the the items to only those that will expire in 30 days:
The condition just checks to make sure it found items that expire, which uses the expression
length(outputs('Get_items_Cheese')?['body/value'])
If yes, then use the select statement to get the Pouch values and convert them to an HTML table:
Then put it all together in your e-mail:
This is the final result:

Was this reply helpful? Yes No
Steve-O28 8 on at

Like (0)

Report
Copy link

Link copied!

Hi David,

Thanks for getting back to me so soon.

I have tried this and although it sends an email, it does not show the pouch numbers. (See below)

I have my list set up in what I imagine is an identical way with the list title as "Pouch1", columns names "Pouch, Cheese, Milk, Break"

I have began by just trying to get a single product working and then I can copy the results for the remaining. At the high level this is my flow:

and looking within each stage is as follows:

Initialize variable Expiration does output a date 30 days in future (03/11/2022)

The expressions are as follows for each stage:
Initialize variable Expiration:
addDays(utcNow(),30,'dd/MM/yyyy')

Condition:
length(outputs('Get_items_Cheese')?['body/value'])

Select From: Value
outputs('Get_items_Cheese')?['body/value']

Map: item()?['Title']

Create HTML table
From:
body('select')

Although the flow runs it appears to fail to return pouch numbers somewhere in the Get items Cheese stage or the condition stage as the expression result is false

I believe it is because the product column in the list is formatted as a date and time. When I set the column formatting to single line of text it returns the pouch numbers correctly.

Is there a method of making this work with the columns set to date and time?

thanks again

Was this reply helpful? Yes No
David_MA 14,393 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!
It could be a couple of things; however, you definitely want your fields with the dates to be date/time columns, but you don't need to store the time.
The first thing is to make sure you have items in your list that would be 30 days from today. Depending on your date format in your list, to me it looks like you don't if the dates showing in your screen shot are in the format mm/dd/yyyy. Thirty days from today would be November 3 at least in North America.
The next thing is that you may not have the correct field name in your filter query. The filter query uses the internal name of the field. You can get this by going into your list settings and clicking on the field. Then look at the end of the URL and it will show the internal name of the field. For example, the display name of the field below is External Contractor, but the internal name is:

Was this reply helpful? Yes No
Steve-O28 8 on at

Like (0)

Report
Copy link

Link copied!

The example list above I have dates for the "Cheese" column set as 02/11/2022, 03/11/2022 and 04/11/2022 (UK date format) dd/MM/yyyy

In the filter query I had been using the name as describes from the URL.

When I set the cheese column as Date and Time it returns no pouch number. Change the column to single line of text it returns the pouch number correctly. It just appears to be the column formatting that makes it work / not work.

Was this reply helpful? Yes No
David_MA 14,393 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!

Glad you got it working!

Was this reply helpful? Yes No
Steve-O28 8 on at

Like (0)

Report
Copy link

Link copied!

just to clarify - it doesnt work with the column set to date and time, but does for single line of text.

I can work with it as single line of text but would be cleaner if set to date and time

Was this reply helpful? Yes No
Verified answer

David_MA 14,393 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!

I think I see why dates are not working for you. I just noticed you said you formatted the expression for the Expiration variable to addDays(utcNow(),30,'dd/MM/yyyy'). While your dates can appear in different formats on screen via your site and profile settings, the date stored in SharePoint is actually stored in ISO8601 format. You need to use that format in query filters and other logic in Power Automate. For your Expiration variable, it needs to be formatted as addDays(utcNow(),30,'yyyy-MM-dd')

Was this reply helpful? Yes No