Onedrive-api-docs: @odata.nextLink when paging the contents of a subfolder does not include subfolder path

Created on 15 Jan 2018  路  6Comments  路  Source: OneDrive/onedrive-api-docs

I am paging through the contents of a subfolder containing 500 items, using the "List children of a DriveItem with a known path" API, like this (drive_id intentionally obfuscated):

GET https://graph.microsoft.com/v1.0/drives/{drive-id}/root:/Paging%20Bug:/children?$select=id,name
 ```

The value of `@odata.nextLink` is:

"@odata.nextLink": "https://graph.microsoft.com/v1.0/drives/{drive-id}/root/children?$select=id%2cname&$skiptoken=UGFnZWQ9VFJVRSZwX1NvcnRCZWhhdmlvcj0wJnBfRmlsZUxlYWZSZWY9Y2F0XzI3OC5qcGcmcF9JRD05ODA"
```

You can see that the folder path has been dropped. I figured this was because the information was encoded in the skiptoken, but this doesn't seem to be the case - this nextLink returns the contents of the root folder.

graph no-recent-activity resolved bug

Most helpful comment

It's currently being investigated by the Graph team - hopefully it won't be much longer until it's resolved.

All 6 comments

Any update? Thanks.

Any update?

It's currently being investigated by the Graph team - hopefully it won't be much longer until it's resolved.

I tried this scenario again today and it looks like the Graph issue was resolved as I'm now seeing the path coming back in the @odata.nextLink.

This issue has been automatically marked as stale because it has marked as resolved but has not had any activity for 10 days. It will be closed if no further activity occurs within 10 days of this comment. Thank you for your contributions to OneDrive API Docs!

Was this page helpful?
0 / 5 - 0 ratings