cancel
Showing results for 
Search instead for 
Did you mean: 
Reply

Multiple Conditions in a Flow (including date) from a List

Hi,

 

I have a simple flow that I want to trigger a chaser email if 2 criteria are met: 1) Status column = Pending / 2) Due Date column = today's date (this is a calculated field in the List). The Flow runs, however, doesn't generate any output when looking at the date. It works fine if the criteria is just 'Pending'. I think the issue may be around the date being pulled from the List and have tried using the 'formatDateTime' expression, but to no avail. 

 

Any suggestions would be very welcome. 

 

Thanks in advance,

 

Steve

SteveTaylor_0-1653919910178.png

 

 

2 ACCEPTED SOLUTIONS

Accepted Solutions

Its not your time zone that counts.  Its the time zone for where the SharePoint server is located.  Check in the Site Settings > regional settings to see what the time zone is.

 

Without more access to your flow I can't tell you what the code should look like exactly.  It will be something with Item() instead of TriggerBody().  If you insert the DueDate field into the compose by itself that should show you what the code should be exactly.



-------------------------------------------------------------------------
If I have answered your question, please mark your post as Solved.
If you like my response, please give it a Thumbs Up.

View solution in original post

@Pstork1  Changing triggerBody() to Item() and amending the source column to a fixed input date field (rather than calculated one that you highlighted can be unreliable) fixed the problem.

 

Thanks for all your help with this - much appreciated! 

 

Steve

View solution in original post

13 REPLIES 13
Pstork1
Most Valuable Professional
Most Valuable Professional

The problem is that the DueDate and UTCNow() both contain a date and a time.  If the times don't match then they aren't equal.  If you add a formatDateTime() to each side and format them both as 'yyyy-MM-dd'. Then the condition will work.



-------------------------------------------------------------------------
If I have answered your question, please mark your post as Solved.
If you like my response, please give it a Thumbs Up.

@Pstork1  Thanks for the quick reply.

 

What would the expressions look like - I have tried the following but still learning expressions:

Trigger: formatDateTime(triggerBody()'[duedate]', 'yyyy-MM-dd')

Result: formatDateTime(utcNow(),'yyyy-MM-dd')

 

The List shows the date with the format 'dd/mm/yyyy'

 

Many thanks for your help,

 

Steve

 

 

It doesn't really matter which format you use as long as it is consistent on both sides of the condition.  The ones you've listed look correct.  You can also use 'dd/MM/yyyy' if you prefer.  The capital MM is important since 'mm' will pull in the minutes not he month.



-------------------------------------------------------------------------
If I have answered your question, please mark your post as Solved.
If you like my response, please give it a Thumbs Up.

@Pstork1 Thanks for the reply. I've updated the expressions as suggested and it runs, but again, no output: 

 

It runs fine when just looking at the Status column, but not when I introduce the Due Date. I have not seen this result where the flow runs, but not even showing 'false' results on the Conditions. Unsure what I am missing here?

 

Thanks again for your ongoing help with this - much appreciated. 

Steve

 

SteveTaylor_0-1653922154941.png

 

You said in your original post that due date was a calculated field.  Do you mean its calculated by SharePoint?  Or its calculated in the flow?  Add a compose before the condition at the top of the loop and check what actual values are being returned.  The greyed out Apply to Each would suggest that your Get items isn't getting any records.



-------------------------------------------------------------------------
If I have answered your question, please mark your post as Solved.
If you like my response, please give it a Thumbs Up.

@Pstork1 I'll try adding the Compose in and see if that helps. In the meantime, if I select the date condition as the only parameter it gives the error message below - Is this pointing to the actual issue, ie the issue is the Sharepoint date being a calculated result rather than an inputted date?

 

InvalidTemplate. Unable to process template language expressions for action 'Condition' at line '0' and column '0': 'The template language function 'formatDateTime' expects its first parameter to be of type string. The provided value is of type 'Null'. Please see https://aka.ms/logicexpressions#formatdatetime for usage details.'.

 

 

The calculated result is within Sharepoint - pulls the date from another column and adds 21 days:

 

SteveTaylor_0-1653923740247.png

 

Thanks,

 

Steve

 

 

 

 

 

The Compose won't fix anything, but it will tell you what the values actually are that you are trying to compare.  The issue is the Due Date calculated field.  Calculated fields are usually unreliable in Power apps.  Add the compose and we'll see what value is actually coming in.



-------------------------------------------------------------------------
If I have answered your question, please mark your post as Solved.
If you like my response, please give it a Thumbs Up.

@Pstork1 I think the data is pulling through ok from the List (copy of Compose input/output below). I changed the trigger field to a static input (1stChaser column) and it comes up with the same error message as above:

 

SteveTaylor_1-1653924822891.png

 

Interestingly, the calculated field result is actually showing 29 May, rather than 30 May on the List. Not sure if that is the root cause, however, as the same issue occurs with a manually input date.

 

Thanks,

 

Steve

The May 29 vs 30 is because SharePoint displays it shifted for your time zone.  The May 29 is UTC.  I assume you are somewhere in North America.  This is a common thing. Flow always retrieves the actual stored value, which will be in UTC.  SharePoint retrieve the same value, but then converts it for the time zone of the site.  Midnight local time would be yesterday in UTC in North America.

 

The problem in the condition is that you are using the wrong column name.  That's why its null.  Your post said you are using 

formatDateTime(triggerBody()'[duedate]', 'yyyy-MM-dd')

It should be

formatDateTime(triggerBody()['Due_x0020_Date'], 'yyyy-MM-dd')


-------------------------------------------------------------------------
If I have answered your question, please mark your post as Solved.
If you like my response, please give it a Thumbs Up.

@Pstork1 

 

My timezone is UTC but it should show the same date?

 

I updated the expressions to the below and got a slightly different error message: 

Unable to process template language expressions for action 'Condition' at line '0' and column '0': 'The template language expression 'formatDateTime(triggerBody()['Due_x0020_Date'], 'yyyy-MM-dd')' cannot be evaluated because property 'Due_x0020_Date' cannot be selected. Please see https://aka.ms/logicexpressions for usage details.'.

 

 

formatDateTime(triggerBody()['Due_x0020_Date'], 'yyyy-MM-dd')
formatDateTime(utcNow(),'yyyy-MM-dd')
 
Thanks,
 
Steve

 

@Pstork1 

 

My timezone is UTC but it should show the same date?

 

I updated the expressions to the below and got a slightly different error message: 

Unable to process template language expressions for action 'Condition' at line '0' and column '0': 'The template language expression 'formatDateTime(triggerBody()['Due_x0020_Date'], 'yyyy-MM-dd')' cannot be evaluated because property 'Due_x0020_Date' cannot be selected. Please see https://aka.ms/logicexpressions for usage details.'.

 

 

formatDateTime(triggerBody()['Due_x0020_Date'], 'yyyy-MM-dd')
formatDateTime(utcNow(),'yyyy-MM-dd')
 
Thanks,
 
Steve

 

Its not your time zone that counts.  Its the time zone for where the SharePoint server is located.  Check in the Site Settings > regional settings to see what the time zone is.

 

Without more access to your flow I can't tell you what the code should look like exactly.  It will be something with Item() instead of TriggerBody().  If you insert the DueDate field into the compose by itself that should show you what the code should be exactly.



-------------------------------------------------------------------------
If I have answered your question, please mark your post as Solved.
If you like my response, please give it a Thumbs Up.

@Pstork1  Changing triggerBody() to Item() and amending the source column to a fixed input date field (rather than calculated one that you highlighted can be unreliable) fixed the problem.

 

Thanks for all your help with this - much appreciated! 

 

Steve

Helpful resources

Announcements

Community will be READ ONLY July 16th, 5p PDT -July 22nd

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!

Summer of Solutions | Week 4 Results | Winners will be posted on July 24th

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  

Check Out | 2024 Release Wave 2 Plans for Microsoft Dynamics 365 and Microsoft Power Platform

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.    

Updates to Transitions in the Power Platform Communities

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

Users online (1,901)