SharePoint / SharePoint/sp-dev-docs
`GetItems` REST method stopped working with OData query operations
@Ashlesha-MSFT is already working on this.
Since Feb 26, 2025.
- Dominant language
- PowerShell
- Stars
- 1.4k
- Forks
- 1.1k
- Avg merge
- 4d 12h
- Merged PRs (30d)
- 12
Description
Target SharePoint environment
SharePoint Online
What SharePoint development model, framework, SDK or API is this about?
SharePoint REST API
Developer environment
None
What browser(s) / client(s) have you tested
- 💥 Internet Explorer
- 💥 Microsoft Edge
- 💥 Google Chrome
- 💥 FireFox
- 💥 Safari
- mobile (iOS/iPadOS)
- mobile (Android)
- not applicable
- other (enter in the "Additional environment details" area below)
Additional environment details
No response
Describe the bug / error
I was maintaining a Power Automate workflow which used to query SharePoint Online list through the GetItems REST API method, combined with $filter & $select OData parameters.
https://contoso.sharepoint.com/_api/lists/getById('guid')/GetItems(query=@v1)?@v1={'ViewXml': "<View><Query></Query></View>"}&$filter=Modified ge datetime'2025-02-24T09:35:29.9345467'&$select=Id,Title,Created
Since december, this combination seems to not work anymore: the OData parameters are skipped.
Steps to reproduce
- Select a platform where you can run the
GetItemsPOST query (SPFx, Power Automate, browser console,...) - Run the query using both CAML & OData parameter
Expected behavior
I expect the OData query operations to work on results given by the CAML query, even if there's nothing clearly documented regarding combination possibilities (except for the $skip one).
Even if I know that what is in the OData can mostly be put in the CAML query, this is something that was supported before.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.