Repository navigation
ODATA filtering based on substringof() #9823
Description
Hi all,
I tried a lot of ways how to create ODATA filter based on substringof function. But I need the oposite function as I need to filter out all item include 'archive' in FileDirRef property, so kind of 'not substringof('archive',FileDirRef). But it isn't a correct syntax of filter query.
I see on this page you can use 'ne' operator, but this also doesn't work for me. Or at least I can't use it.
Any help on that?
BR,
K.Z.
Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.
- ID: 916d6284-9149-5d95-48d8-40c60ba9f3c7
- Version Independent ID: 9c41a103-56d6-c186-26aa-ccd098a61f7e
- Content: Use OData query operations in SharePoint REST requests
- Content Source: docs/sp-add-ins/use-odata-query-operations-in-sharepoint-rest-requests.md
- Service: sharepoint
- GitHub Login: Vesa Juvonen (@VesaJuvonen)
- Microsoft Alias: vesaj
Activity
Ashlesha-MSFT commentedon May 26, 2025
Hello kam-zaj-az,
Thank you for bringing this issue to our attention. We will look into it and get back to you shortly.
Ashlesha-MSFT commentedon May 26, 2025
kam-zaj-az,
The inability to filter with negated string functions like not substringof(...) is a real limitation in the SharePoint REST API's OData support.
could you please raise a feature request to Microsoft for this?
(https://feedbackportal.microsoft.com/feedback/forum/06735c62-321c-ec11-b6e7-0022481f8472)
VesaJuvonen commentedon Nov 3, 2026
This issue is more than 12 months old and has not had recent activity. We are cleaning up the backlog so we can manage incoming reports more efficiently. If the issue is still relevant, please submit a new issue with updated details and current reproduction steps. We apologize for any inconvenience caused by this updated process, and thank you for being part of the SharePoint developer ecosystem.
github-actions commentedon Nov 3, 2026
Thank you for taking the time to file an issue. We periodically archive older or inactive issues as part of our issue management process, which automatically closes them once they are archived.
If you’d like to understand more about why and how we handle archived (closed) issues, please see Our approach to closed issues.
We appreciate your contribution and if this is still an active issue with the latest SPFx versions, please do resubmit the details. We needed to perform a cleanup, so that we can start with a clean table with a new process. We apologize for the inconvenience this might cause.