Hi,
I'd like to create a Flow that reads data from an Excel sheet, specifically the timestamp (1) and the user (2). If the timestamp is older than 7 days, I want to send a reminder email to the user. In the first step, I've already created a flow that captures data from a Microsoft Forms survey and records it in an Excel table (see Screenshot1).
Now, I've started working on another Flow to read data from the Excel table and check if the most recent timestamp for User X is older than 7 days. If it is, I want to trigger a reminder email; otherwise, nothing should happen. The problem I'm facing right now is that I'm unsure about what to specify in the conditions. On the left side, I have the variable (timestamp), and on the right side, I've used the code "addDays(utcNow(), -7)" to represent "older than 7 days." However, when I tested this condition, it always resulted in the same outcome regardless of the data in the Excel sheet (I even tried switching from <7 Days to >7Days )
I hope this explanation clarifies my issue. I apologize that the screenshots are in German. If there's anything specific I should translate, please let me know.
Thanks
Solved! Go to Solution.
@Daniel_B You should use a Filter Array action instead. The way you currently have your flow set up means that you will loop through all items in your Excel table checking each item to see if the timestamp is older than 7 days. This would be inefficient especially as your Excel table rows increase. To learn more about how to use the Filter Array action, please reference this YT tutorial that I uploaded a few weeks ago.
The reason that your condition isn't working is because you are comparing a timestamp. Depending on when you are running the flow, your condition argument is looking to see if the items in your Excel table are 7 days from the current date/time the flow has run. Instead, you should check to see if any items in your Excel sheet have a date that is 7 days old (not including the time).
Another thing to note is the timestamp that is stored in your Excel sheet. Are you storing the UTC timestamp or a timestamp in your local timezone? This will effect the condition argument and you may need to make adjustments to your flow accordingly. Keep this in mind when running your flow while testing. This is why Compose actions and reviewing your outputs will be absolutely crucial when building your flow.
I'm unsure of how many rows you have in your Excel table. I would recommend limiting the number of rows returned by using the Top Count field in the List Rows Present in a Table action. Alternatively, you can create a test Excel Table that includes a few examples with dates older than 7 days from today.
Select the ISO 8601 DateTime format. Otherwise the date returned from this action will be a number instead of a date.
Optional: Add a Compose action to store the outputs from the List Rows Present in a Table action. I find it easier to view the content right in the outputs.
You can click to download the outputs from the List Rows present in a table action if you prefer.
Add a Compose action to store the dynamic date (7 days ago).
I'm not sure what the format of your date in Excel is, but you need to confirm this from the outputs of your List Rows present in a table action or in a Compose action (as I've demonstrated above).
Your expression was correct though you need to format your date to match the output from Excel.
addDays(utcNow(),-7,'yyyy-MM-dd')
In my Excel output example above the timestamp looks like this:
2023-08-05T00:00:00.000Z
We'll use the Filter Array action to check for items that are greater than 7 days ago from today. To do this, we'll need to see if any rows have a date value (regardless of the time) are greater than 7 days ago.
The List Rows Present in a Table action returns an array of the rows in the Excel table. By using a Filter Array action you can filter out the items that meet your criteria rather than unnecessarily looping through all rows in your Excel table.
Because you are storing the timestamp in Excel you will need to format that value so it only returns the date (formatted the same way as the dynamic date above).
You'll need an expression for this. Insert the formatDateTime() function.
Unfortunately when use an expression, the dynamic content from the List Rows Present in a table action arent' available.
You'll need to use the item() function and a key to access the column that is storing your timestamp. You will need to reference the outputs from the List Rows Present in a Table action. All the keys for the content is the red text between the double quotes.
The key for my column is Task Due Date. Yours will be different.
You need to insert:
item()?['']
between the formatDateTime() function. The key will go between the single quotes—exactly how it appears in the outputs.
My expression looks like this:
formatDateTime(item()?['Task Due Date'])
Yours will look different.
Depending on your criteria you can choose the is less than or is less than or equal to operator. In the second value field, insert the outputs from the Dynamic Date Compose action.
Important: Refer to this section of my YT Tutorial that covers how to return dynamic content from a Filter Array action. It will be helpful to review if you need to return values in an action later on in your flow.
Add a Compose action to return the number of items returned from the Filter Array action. If no items are returned, you can stop the flow. Otherwise you can continue on with your flow.
Use the length() function.
Insert the Body output from the Filter Array action.
Run a test!
Add a Condition action to your flow. Insert the outputs from the Filter Array Count action (above) into the first value field. Change the operator to is not equal to. In the second value field, enter a 0.
Insert your actions into the appropriate branch of the Condition action.
Hope this helps!
If I helped you solve your problem—please mark my post as a solution ✅. Consider giving me a 👍 if you liked my response! |
@Daniel_B You should use a Filter Array action instead. The way you currently have your flow set up means that you will loop through all items in your Excel table checking each item to see if the timestamp is older than 7 days. This would be inefficient especially as your Excel table rows increase. To learn more about how to use the Filter Array action, please reference this YT tutorial that I uploaded a few weeks ago.
The reason that your condition isn't working is because you are comparing a timestamp. Depending on when you are running the flow, your condition argument is looking to see if the items in your Excel table are 7 days from the current date/time the flow has run. Instead, you should check to see if any items in your Excel sheet have a date that is 7 days old (not including the time).
Another thing to note is the timestamp that is stored in your Excel sheet. Are you storing the UTC timestamp or a timestamp in your local timezone? This will effect the condition argument and you may need to make adjustments to your flow accordingly. Keep this in mind when running your flow while testing. This is why Compose actions and reviewing your outputs will be absolutely crucial when building your flow.
I'm unsure of how many rows you have in your Excel table. I would recommend limiting the number of rows returned by using the Top Count field in the List Rows Present in a Table action. Alternatively, you can create a test Excel Table that includes a few examples with dates older than 7 days from today.
Select the ISO 8601 DateTime format. Otherwise the date returned from this action will be a number instead of a date.
Optional: Add a Compose action to store the outputs from the List Rows Present in a Table action. I find it easier to view the content right in the outputs.
You can click to download the outputs from the List Rows present in a table action if you prefer.
Add a Compose action to store the dynamic date (7 days ago).
I'm not sure what the format of your date in Excel is, but you need to confirm this from the outputs of your List Rows present in a table action or in a Compose action (as I've demonstrated above).
Your expression was correct though you need to format your date to match the output from Excel.
addDays(utcNow(),-7,'yyyy-MM-dd')
In my Excel output example above the timestamp looks like this:
2023-08-05T00:00:00.000Z
We'll use the Filter Array action to check for items that are greater than 7 days ago from today. To do this, we'll need to see if any rows have a date value (regardless of the time) are greater than 7 days ago.
The List Rows Present in a Table action returns an array of the rows in the Excel table. By using a Filter Array action you can filter out the items that meet your criteria rather than unnecessarily looping through all rows in your Excel table.
Because you are storing the timestamp in Excel you will need to format that value so it only returns the date (formatted the same way as the dynamic date above).
You'll need an expression for this. Insert the formatDateTime() function.
Unfortunately when use an expression, the dynamic content from the List Rows Present in a table action arent' available.
You'll need to use the item() function and a key to access the column that is storing your timestamp. You will need to reference the outputs from the List Rows Present in a Table action. All the keys for the content is the red text between the double quotes.
The key for my column is Task Due Date. Yours will be different.
You need to insert:
item()?['']
between the formatDateTime() function. The key will go between the single quotes—exactly how it appears in the outputs.
My expression looks like this:
formatDateTime(item()?['Task Due Date'])
Yours will look different.
Depending on your criteria you can choose the is less than or is less than or equal to operator. In the second value field, insert the outputs from the Dynamic Date Compose action.
Important: Refer to this section of my YT Tutorial that covers how to return dynamic content from a Filter Array action. It will be helpful to review if you need to return values in an action later on in your flow.
Add a Compose action to return the number of items returned from the Filter Array action. If no items are returned, you can stop the flow. Otherwise you can continue on with your flow.
Use the length() function.
Insert the Body output from the Filter Array action.
Run a test!
Add a Condition action to your flow. Insert the outputs from the Filter Array Count action (above) into the first value field. Change the operator to is not equal to. In the second value field, enter a 0.
Insert your actions into the appropriate branch of the Condition action.
Hope this helps!
If I helped you solve your problem—please mark my post as a solution ✅. Consider giving me a 👍 if you liked my response! |
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!
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 Week 4 Results: Congratulations to the Week 4 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Week 4:Community MembersSolutionsSuper UsersSolutionsPower Automate Deenuji11FLMike31Sayan11ManishSolanki16VishnuReddy199710creativeopinion14Akshansh-Sharma3SudeepGhatakNZ7claudiovc2CFernandes5 misc2Nived_Nambiar5 Usernametwice232rzaneti5 eetuRobo2 Anil_g2 SharonS2
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.
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