microsoftgraph / microsoftgraph/msgraph-metadata

Invalid request when querying SharePoint list items

Open
#816 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

ToTriage
Dominant language
XSLT
Stars
166
Forks
55
Avg merge
16h 12m
Merged PRs (30d)
14

Description

Dear Microsoft Team,
We have a solution called Boxafe developed by us ( QNAP Systems Inc) helps customers to backup their M365 SAAS data to QNAP's local storage. This includes backup of Email, contacts, Calendar, One Drive Files, Sharepoint files, Teams data.

One of our customers is facing issue with few of his sharepoint sites to backup. Can you help with this. following are the details.
We encountered a potential bug when using Microsoft Graph API to query SharePoint list items, this request is generated based on the @odata.nextLink returned from M365.

Request:
https://graph.microsoft.com/v1.0/sites/sahsml.sharepoint.com,aabe8d71-af12-434e-bf5d-4f06120ffd58,97812599-2b7c-45c7-88c0-8712de10b789/lists/2a2ef00b-a8ab-47ad-95d0-becddf239a5f/items?$select=sharepointIds%2CparentReference&$expand=driveItem(%24select%3DparentReference)&$top=1000&$skiptoken=UGFnZWQ9VFJVRSZwX0lEPTE0MTgwOCZpeF9QYWdlZD1UUlVFJml4X0lEPTE0MTgwOCZpeF9LZXk9RjNCODI5RTMzQkI3NEJCNEFCRjE1OTM5NUI3MUMyMEE

Response:
{'error': {'code': 'invalidRequest', 'message': 'One of the provided arguments is not acceptable.', 'innerError': {'code': 'badArgument', 'date': '2025-04-13T18:04:34', 'request-id': 'e9803381-6a9f-4fa3-aaac-f591f7d20235', 'client-request-id': 'e9803381-6a9f-4fa3-aaac-f591f7d20235'}}}

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the supplied Microsoft Graph v1.0 SharePoint list-items request and its invalidRequest response, then compare the generated @odata.nextLink parameters with the original query. Done means determining whether the request is reproducibly invalid and documenting the confirmed cause or required API correction.

Written by the indexing model from the issue text.

Assessment

Domain
api
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.