ODATA filter of Power Automate is preventing the flow from running

Dear Lauren,

Good day, and thank you for reaching out to the Q&A Forum.

I understand that you are having an unexpected issue with the OData Filter Query in your Power Automate flow preventing the Get items action from returning the expected results. As a forum moderator, I am not able to access your Power Automate flow to test the exact filter expression from my side. My role here is limited to providing general guidance and pointing you to the right resources. Based on your description and screenshot, there are three common reasons why an OData filter on a SharePoint date column fails to return results:

1.Date format mismatch

SharePoint's OData filter does not accept the display format (like 9/18/2026 or dd-MM-yyyy). It expects ISO 8601 format, for example: 2026-09-18T00:00:00Z. Your formatDateTime(addDays(utcNow(),60),'yyyy-MM-dd') expression is close, but for SharePoint you typically need to include the full ISO 8601 timestamp (yyyy-MM-ddTHH:mm:ssZ).

2.Column internal name vs display name

The Filter Query must use the column's internal name, not its display name. Since your column is displayed as SOP EXPIRY DATE (with spaces), SharePoint likely renamed it internally to something like SOP_x0020_EXPIRY_x0020_DATE. To find the actual internal name:

• Open the SharePoint list.
• Go to Settings > List settings.
• Click on the SOP EXPIRY DATE column.
• In the browser's address bar, look for Field=... and use that exact value in your Filter Query.
• If the column was renamed after being created, its internal name may look very different from the current display name.

3.Time component on the date value

Even when a SharePoint column is displayed as a date only, it can store an underlying time component. Using eq may miss matches because of that time. Instead, using a one-day range (ge X and lt X+1) is generally more reliable, so the query returns all items whose date falls within that day regardless of the time.

For the exact syntax to use inside Power Automate's Filter Query field (which can be quite specific and easy to get wrong), I would highly recommend reposting your scenario in the Power Platform Community, specifically under the Power Automate forum. That community is actively followed by Power Platform MVPs and engineers who solve this exact type of SharePoint and OData Filter Query scenario on a daily basis. They will be able to give you the exact working expression tailored to your list.

When posting there, please include:

• A screenshot of your Get items action, including the Filter Query field.
• The internal name of your date column (from the steps above).
• The display format of the date values in your list.
• The exact error message or empty result you are getting.

Beyond just resolving this specific issue, the Power Platform Community is also a wonderful place to grow your Power Automate skills over time. There is a large library of community-tested templates, deep-dive technical articles, and shared solutions covering exactly the kinds of workflows you are building, so it will be a valuable resource for you well beyond just this one query.

I hope this helps clarify the likely root causes and gives you a clear direction to move forward with. Please accept my apologies for redirecting you to a different community, since your scenario goes into fairly specific Power Platform territory, that community is genuinely best positioned to give you a verified working answer faster than I can from here.

If you have any other Microsoft 365 questions come up along the way, please feel free to come back to this forum anytime. I'm always happy to help. Wishing you the very best with your flow, and I truly hope everything falls into place quickly once you have the exact syntax dialed in.

If the answer is helpful, please click "Yes" and kindly upvote it. If you have extra questions about this answer, please click "Comment".  

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.