Get files (properties only) – Created ge filter no longer returns items

(0) Share

Report

Posted on by CU16010044-0

Hi everyone,

I’m running into what looks like a recent regression or behavior change with the SharePoint Get files (properties only) action when filtering on the Created column.

This flow has worked reliably for months and recently stopped working without any changes to the logic.

Scenario / Business Requirement

A scheduled flow runs once per day at 5 PM
It should find files that were uploaded (created) today
Only files inside a specific folder (Field Reports)(Many of these folders though)
The output (body → value) from Get files (properties only) is then used to:
- Loop through files
- Send emails to each client
Because downstream logic depends on the Get files(properties only) output, I cannot rely on a secondary Filter array workaround — I need the OData filter to work correctly

Current Flow Logic

Compose – DateTime

formatDateTime(startOfDay(utcNow()), 'yyyy-MM-ddTHH:mm:ssZ')

Example output:

2026-01-20T00:00:00Z

Get files(properties only)

Filter Query:

substringof('Field Reports', FileDirRef) and Created ge '@{outputs('DateTime')}'

Observed Behavior

The action returns no items: "value": []
The exact same query works immediately when replacing Created with Modified:

substringof('Field Reports', FileDirRef) and Modified ge '2026-01-20T00:00:00Z'

The files returned by Modified were actually uploaded today, not modified later
SharePoint library clearly shows Created = today for those files

Run History Evidence

The executed request clearly shows:

…but returns:

Why This Is a Problem

Using Modified is not a valid substitute:

It picks up files that were merely touched by automation or metadata updates

My flow logic depends on upload-only detection

The email logic relies on the Get files output, not post-filtering

Questions

Has there been a recent SharePoint / connector change affecting OData filtering on the Created field?

Is this a known regression in Get files (properties only)?

Is there a supported workaround that preserves upload-only semantics without moving filtering out of the action?

Is Microsoft planning a fix, or should flows migrate away from Created entirely?

Any confirmation or official guidance would be hugely appreciated — this breaks a very common “daily upload detection” pattern.

Thanks in advance.

Categories:

Power Automate Desktop

Building flows

Using flows

I have the same question (0)

All responses (5)

Answers (0)

Sort by

Expiscornovus 33,891 Most Valuable Professional on at

Like
a
(1)

Report
Copy link

Link copied!

Hi @CU16010044-0,

Just tried to reproduce your issue with your specific setup. I have no issues with that Created field in an OData filter in my development environment. It returns items I have created today in a Field Reports folder.

Can you share more details about your Get files (properties only) configuration.

Have you set any other settings in that action. Or is it like the below screenshot?

Happy to help out 😁

I share more #PowerAutomate and #SharePointOnline content on my Blog, LinkedIn, Bluesky profile or Youtube Channel

Was this reply helpful? Yes No
Suggested answer

eliotcole 4,390 Moderator on at

Like
a
(1)

Report
Copy link

Link copied!
I started writing far too much as a response, here,@CU16010044-0, but to just speak to the OData of it all in VERY brief terms that @Expiscornovus quite rightly noted should work.

It technically does not list using dates as an available option with 'ge' or 'le' functions ...

https://learn.microsoft.com/en-us/sharepoint/dev/sp-add-ins/use-odata-query-operations-in-sharepoint-rest-requests#odata-query-operators-supported-in-the-sharepoint-rest-service

That being said, the *Graph* API does state it explicitly with examples, here:

https://learn.microsoft.com/en-us/graph/filter-query-parameter?tabs=http#for-single-primitive-types-like-string-int-and-dates

So, you may wish to switch to SP actions using the 'Send an HTTP request to SharePoint' action to get your data.

If you do, I can highly recommend two things:

No Meta Data - Use 'nometadata' flags in 'Content-Type' and 'Accept' headers this reduces what you need to include for many requests, and the junk data that you get back in response:

SharePoint API V1 (OData V2)

application/json; odata=nometadata

SharePoint API V2 / Graph API (OData V4)

application/json; odata.metadata=none

StaticDataObjCNST - Make a 'Parse JSON' with this name as one of the first two actions of your flow, and include manually input data that you will re-use throughout the flow

I actually make two of those Parse JSON 'constants' things, one at the start, and another in a Scope where I 'Set...' variables, right at the end of the scope, and name it:

ConstantsObjCNST

That allows me to have some 'constants' that are dependent on some other data, pulled through earlier on. :-)

Either way, doing this will make any requests that you make using the 'HTTP' action sooooo much easier ... plus it will reduce the amount of 'single use' variables you may create. 👍

---

Finally, if you do make the (potentially difficult) switch to using 'HTTP' action with SharePoint API V2, then I think you might wish to take a look at this section of the Graph 'files' endpoint as it looks very powerful ... ;-)

https://learn.microsoft.com/en-us/graph/api/driveitem-delta?view=graph-rest-1.0&tabs=http

1 people found this reply helpful.

Was this reply helpful? Yes No
eliotcole 4,390 Moderator on at

Like
a
(0)

Report
Copy link

Link copied!

Oh, there is also the 'Retrieve items as a stream' API endpoint for the V1 SharePoint REST API.

https://learn.microsoft.com/en-us/sharepoint/dev/sp-add-ins/working-with-lists-and-list-items-with-rest?source=recommendations#retrieve-items-as-a-stream

That might be more dependable or let you use your mind's logic more appropriately. :-)

Was this reply helpful? Yes No
eliotcole 4,390 Moderator on at

Like
a
(0)

Report
Copy link

Link copied!

Purely out of curiousity, may I ask why you do not run a trigger on the source library / folder for new / modified items?

Was this reply helpful? Yes No
PieterVeenstra 33 on at

Like
a
(2)

Report
Copy link

Link copied!

How many items do you have in your list or library? Are you exceeding one of those magic numbers?

You could try to create an index on the Created column in your SharePoint list.

3 people found this reply helpful.

Was this reply helpful? Yes No