How to easily filter a SharePoint list by Day, Month or Year with hidden oData filter functions

In this video I demonstrate additional oData filtering capability in #PowerAutomate that can be used to filter a date field in a SharePoint list based on the day, month or year of the list item.
This can help you to build more efficient #MicrosoftFlows that do not require additional conditions or filter actions and makes working with large lists much easier. This method requires no calculated columns and can work directly from the Date field in SharePoint.

[denisemcbean]

I am new to SharePoint online. Thank you so much for your explanation.

[grantwylie]

Thank you. I am looking to filter colleagues annual leave with a leave start date of 1st August. What would be the filter query to show the leave requested range from August last year up until eg utcnow/today? Does that make any sense? Something like ge yyyy-08-01 and le utcnow

[stefancochrane]

So several http requests to do something extremely simple. Wonderful software. :-|

[winterintrigue]

for anyone that would like to copy/paste the start of that URI

/_vti_bin/listdata.svc/

[DeShonClark]

Thanks Paulie for sharing, I wonder if the Microsoft graph API supports this odata syntax

[GinGersound]

So I’m trying solve the simple birthday problem. Get all the customers from a SharePoint list who’s birthday is today.

I am using an HTTP request to SharePoint, GET, and the URI is eq 11 and day(DOB) eq 15”

It just returns bad gateway over and over!

I know it’s not a syntax issue as it works perfectly when I use the column Created or Modified. It gets even more frustrating because it also errors on every list and column combination I try except when using Created or Modified. Also if I use a straight forward eq filter or gt and lt using the DOB column it works fine and I can see it is DateTime just like Created is.

I would really rather not have to pull in the full list and then filter it or add calculated columns to my list when this should be a simple oData filter.

Has alone else had this issue or has any idea why my DateTime columns return errors but the built in ones work fine?