Haha! That's a good hack. I had to do something similar to sync a couple of calendars in a different Flow (which has probably also stopped working). I'd really rather not go through all that though. I'm a bit new to these forums - does MS actually read these and note issues, or is there some other mechanism for that?
I am also having the same problem. My flow failed to work because this FilterQuery.
Even the expression 'and' is no longer recognized.
What the hell Microsoft is doing?
Ok. I found the solution.
Here's the examples that will work in the filter query:
Start/DateTime gt '2020-01-08T00:00:00'
If you need to use 'utcNow':
Start/DateTime gt 'utcNow('yyyy-MM-ddT00:00:00')'
Hope this helps!
Fantastic, @jbedfordp! That totally worked. So many thumbs-up button clicks for you. Was this a bunch of trial and error, or did you find something online that explains this behaviour?
I can't claim credit for this solution at all -- all of my trial and error ended in error! 🤣
@BeeBee identified the syntax that works. It appears to cast the "start" field as a "DateTime" type or format?
I'd love to know where this syntax comes from, though! I didn't see this in any of my searching thru ODATA or Flow or Graph API syntax manuals. Wherever this is documented undoubtedly has a bunch of other tips and tricks to offer!
@jbedfordp All thanks to the trial-and-error in your previous post. It's the start of my inspiration.
I was struggling with the Filter Query for utcNow.
Then I found this from github:
At first, I was using:
Start/DateTime gt 'utcNow('yyyy-mm-ddThh:mm:ss')'
and it gets translated to this instead:
Start/DateTime gt '2020-30-08T06:30:57'
so unless we are in different planet, clearly the calendar does not have 30 months.
then I change the date time format to:
Seriously, Microsoft needs to provide a better manual especially how to use OData and its syntax in Power Automate.
Hmm.... but where did the idea for the "/DateTime" syntax come from? That's the bit that I hadn't seen before, and which I think enables ordering by the "start" property. I can't tell if it's OData syntax or Graph syntax or Power Automate syntax or ...
Closest explanation of that I can find is that the "/DateTime" syntax implies that the "start" property has a related (or sub-?) property called "DateTime"...
(search for "forward slash")
Brilliant that you figured this out. This was a life saver for me. I had a Flow that broke within the last month and a half after working for about a year before that because of this syntax change.
Check out the on demand sessions that are available now!
ISV Studio is designed to become the go-to Power Platform destination for ISV’s to monitor & manage published applications.
See the latest Power Automate innovations, updates, and demos from the Microsoft Business Applications Launch Event.