Graph Drive GetItems Filter has no effect

Sidi_244 20 Reputation points
2024-12-18T18:32:32.6733333+00:00

Hi There

When I use this query: https://graph.microsoft.com/v1.0/drives/DRIVEID/items?%24filter=name%20eq%20%27TEST%27 to filter my drive for items with name = TEST i get returned ALL items on my drive.

This was did not behave like this before. What did change? How can this happen?

Happy for any hints!

Microsoft Graph
Microsoft Graph
A Microsoft programmability model that exposes REST APIs and client libraries to access data on Microsoft 365 services.
13,212 questions
SharePoint Development
SharePoint Development
SharePoint: A group of Microsoft Products and technologies used for sharing and managing content, knowledge, and applications.Development: The process of researching, productizing, and refining new or existing technologies.
3,393 questions
{count} votes

Accepted answer
  1. Xyza Xue_MSFT 29,356 Reputation points Microsoft External Staff
    2024-12-24T01:28:28.5+00:00

    Hi @Sidi_244 ,

    I'm glad to hear you solve the problem,I would make a brief summary of this thread:

    Issue Symptom:

    When I use this query: https://graph.microsoft.com/v1.0/drives/DRIVEID/items?%24filter=name%20eq%20%27TEST%27 to filter my drive for items with name = TEST i get returned ALL items on my drive.

    Current status:

    The issue has been solved. Another endpoint that still works: https://graph.microsoft.com/v1.0/drives/DRIVEID/root/children?$filter=name+eq+'NAME'

    You could click the "Accept Answer" button for this summary to close this thread, and this can make it easier for other community member's to see the useful information when reading this thread. Thanks for your understanding!


    0 comments No comments

3 additional answers

Sort by: Most helpful
  1. Xyza Xue_MSFT 29,356 Reputation points Microsoft External Staff
    2024-12-19T03:11:44.62+00:00

    Hi @Sidi_244 ,

    After my testing, none of the Filter properties in the Graph API are currently working, and other users are currently reporting this as well. It's possible that there have been recent changes or updates to the Microsoft Graph API that affect how filtering works. Microsoft has not yet released updated documentation for this change. If you think this matter does not affect you much, my suggestion is that you can wait for a few days. If you do mind and want a quick fix, I suggest you create a new service request in the Azure admin center as an administrator and a more professional person will help you.

    User's image


    If the answer is helpful, please click "Accept Answer" 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.


  2. Sidi_244 20 Reputation points
    2024-12-23T19:56:11.94+00:00

    Support was able to show me another endpoint that still works: https://graph.microsoft.com/v1.0/drives/DRIVEID/root/children?$filter=name+eq+'NAME'

    0 comments No comments

  3. Martin Lingstuyl 1 Reputation point MVP
    2025-03-07T15:33:26.9166667+00:00

    Hi guys, I have run into the same issues on my end.

    I've succeeded in reaching someone from Microsoft on this. The response boils down to this:

    The /drives/{id}/items endpoint only supports filtering by /listitem/fields/{fieldName} and there's an option to scope the query to a folder (immediate children) by specifying $filter=parentReference/id eq '{folderItemId}'. Both built-in and custom fields are supported for filtering.

    So it appears to be by design. Even if your queries used to work correctly before. A docs update on this should be in the making.

    I hope this gets you unstuck...

    in your case this means you could $filter by listItem/fields/FileLeafRef:
    $filter=listItem/fields/FileLeafRef eq '{fileName}'

    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.