I don't understand how to filter on datetime columns in MS Flow / Power Automate. This should be one of the easiest filters to apply...
This page includes an example with pictures, but when replicated does not work:
WorkOrderCreatedTime gt addDays(utcnow('yyyy-MM-ddTHH:mm:ssZ'),-30)
Spam filter I think is triggering on my links sorry for the funky format:
https://www.odata.org/documentation/odata-version-2-0/uri-conventions/
Note: One of the comments states that it should be surrounded in single quotes, but that also does not appear to work
This page states that the filter criteria for a date/datetime should be surrounded in single quotes and preceded by the word datetime, but this does not appear to work.
DateTime values must be delimited by single quotation marks and preceded by the word datetime, such as datetime'2010-01-25T02:13:40.1374695Z'.
Spam filter I think is triggering on my links sorry for the funky format:
https://docs.microsoft.com/en-us/previous-versions/dynamicsnav-2016/hh169248(v=nav.90)
Doing year(X) and month(X) etc is not an acceptable solution as it will not work if querying data older than 1 calendar year.
Here are screen shots of things I've tried that don't work (StormDate is my datetime column). Successful response is included at the bottom to demonstrate the format of the response when I leave this particular filter off.
They pretty much all end like this:
Here's a successful response where I leave the filter off:
Solved! Go to Solution.
I am using addMinutes rather than addDays but I still can't get this to resolve the way you did. Is your server on premise or in the cloud? Not that I think that's the issue here, since the error message is complaining about JSON syntax but I figured I should ask.
Mine is on prem. I'm not sure if it's different for cloud v prem. One other thing I've seen that's goofy though is time zones. Maybe you've got a time zone thing with your filter? (I know it's specified in zulu with the Z, but I've seen the time stamp come back from get rows be labeled as zulu when it's in fact in local, or maybe it was vice versa, I can't remember, but I still don't have that issue resolved. I'm kicking that can down the road until DST changes again.)
I have tried just about every method I know, and many I didn't know, and still cannot get this to work.
The problem I have, as I'm sure many do, is that this is inconsistent. If the records are in Sharepoint you can merely type something like:
CreditDate gt ' startOfMonth(utcNow())' and it will return the right results.
If the data is held in SQL (on premise and accessed through the on premise data gateway) it seems that this is close to impossible.
I got excited when I saw this as it seemed to describe everything I needed, but unfortunately doesn't resolve my problem.
So I'm trying to filter based on a field called SpareDate1 (SQL holds as a datetime field) where the datetime held is less than today - 30 days.
For reference this works:
SpareDate1 eq 'formatDateTime(utcNow(),'dd/MM/yyyy')
But this doesn't:
SpareDate1 lt 'formatDateTime(utcNow(),'dd/MM/yyyy')
So I'm left scratching my head, and really not wanting to bring in all of the records, and then having to filter them within my flow.
HELP!!!
@A8Tony if you are doing date comparisons you should always use the yyyy-MM-dd format and make sure that both parts of the comparison are using it. So try that in your filter query.
Rob
Los Gallardos
If I've answered your question or solved your problem, please mark this question as answered. This helps others who have the same question find a solution quickly via the forum search. If you liked my response, please consider giving it a thumbs up. Thanks.
Hi @RobElliott thanks for the swift response.
I've tried that.
As an example, here is the data held in my SQL table:
It is SpareDate1 I am trying to filter on.
So, I've just tried
SpareDate1 lt (formatDateTime(utcNow(),'yyyy-MM-dd')
SpareDate1 lt (formatDateTime(utcNow(),'yyyy-MM-dd 00:00:00.000')
Neither of which have worked.
Right now, I see my only solution is to work on a data view which filters this data out before it even gets to my flow. The really frustrating thing is I'm sure I've done this before 🤔
This works for me with sql on prem through on prem data gateway.
StormDate ge date(2020-01-01T00:00:00Z)
That is plain text that goes in the filter box. If you do StormDate ge '____' it treats the ___ as a string, and doesn't know it's a datetime, which is why that doesn't work. You wrap the ___ in date() which is just a plain string from the flow's point of view, but it's a keyword for the oData stuff to tell it that hey, don't treat ___ as a string or a number, treat it as a datetime.
To get 30 days of data, I delete the date out of the above but leave the rest. Then I click inside the parenthesis and add this as an expression in flow. This means that flow will evaluate this formula as an expression and pass the resulting string WITHIN the Odata stuff. This is where you'd have to put the format stuff if you need to do that still, but the rest of the box would stay the same.
addDays(utcNow(),-30)
and so the final thing looks like this in the flow (note that the purple box is actually the whole adddays formula above, flow just hides some of it).
How did you get this to work? I'm using the same and getting:
We cannot apply operator < to types Date and DateTime.
inner exception: We cannot apply operator < to types Date and DateTime.
Are you using SQL on-premise? (I am)
Thank you
No! I'm getting that from Flow:
We cannot apply operator < to types Date and DateTime.
inner exception: We cannot apply operator < to types Date and DateTime.
clientRequestId: e6ee30c3-84d4-46d0-94ed-34c4f0c03e7c
If you don't mind, what type of field is StormData?
I'll answer my own question... when I read "We cannot apply operator < to types Date and DateTime." I took it as "we cannot apply operator < to Date OR TO DateTime". Actually, the problem was that I was comparing a Date with a DateTime.
Changing
SQL_DATE_FIELD le date(AddDays(utcnow(),-20)
to
date(SQL_DATE_FIELD) le date(AddDays(utcnow(),-20)
fixed the issue
Nice! Good catch! That was definitely not very clear in that error message, I read it same as you did just now, but maybe because I knew the struggle you were probably facing lol
Cheers Pablo!
If anyone stumbles into this, tries the solution, and still receive the invalid JSON error...
I have found that the following syntax works:
date(ColumnName) ge date(DateValueYouProvide)
Cheers!
Hi everyone, please consider voting on this 'idea' to fix the implementation of the ODATA spec for date and datetime filtering. I started a ticket with MS and they have told me that it is 'by design' and not on the roadmap to fix. If you would please vote there's a chance they may fix it.
This fixed my issue - I wasn't using the date function with my first field. Thanks
For some reason I'm not able to use this solution unless I'm using ge instead of gt, and when I use it, the database just returns all the values it can without applying the filter at all.
date(LAST_MODIFIED_DATE) ge date(first(outputs('LastModifiedEntry')?['body/value'])?['LatestModification'])
date(LAST_MODIFIED_DATE) ge date(2023-08-24T20:28:11Z)
Decided to try this again to see if it can be solved. I should've specified that i'm using SQL on-prem though on-prem gateway, adn that LAST_MODIFIED_DATE is a datetime2 column.
If I use gt instead of ge, the connector returns no results UNLESS I wrap it in addHours(<datetime>, -10), but the values it returns are high enough that addHours(<datetime>, -1) should've covered them. Example:
Returns:
If I use -9, -8, -7, etc, it returns no results (haven't tested with lower values). Strangely enough, if you convert it to minutes, it allows you to get away with -599 or-598 instead of -600, but at -597 it refuses to budge for some reason. I'm guessing some number somewhere is going far back enough that it registers as yesterday, despite clearly being today in UTC.
Hello everyone,
I have a similar problem with the OData filter when retrieving an on prem SQL database via the data gateway.
Even after days of research and attempts with all syntax variants, the query fails or returns NULL values.
Do you have any ideas what else I could try?
I already tried these formats and thousands more:
'yyyy-MM-dd hh:mm:ss'
'yyyy-MM-dd hh:mm:ss.000'
'yyyy-MM-ddThh:mm:ssZ'
''yyyy-MM-dd'
'MM/dd/yyyy'
'dd/MM/yyyy'
Thank you in advance for your help!
Best regards
Pascal
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