microsoftgraph / microsoftgraph/msgraph-beta-sdk-dotnet

Orderby probably does not work in DeviceManagement.Reports.GetDeviceInstallStatusReport

Open
#683 7 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Bug: metadata Question: SDK Status: Needs investigation
Dominant language
C#
Stars
112
Forks
37
Avg merge
14h 57m
Merged PRs (30d)
3

Description

I am sending requests to get all install status reports using the code below. But when I am using pagination, because I can't get all items in one response (rows total number is ~5000. it gives 50 items per page, so skip parameter every time increased ), orderby looks like works in the wrong way. As a result on different pages, I can find the same item that was on the first page. But the same items I can see after a new graph client was created. So I am worried about the possibility to miss an item

var deviceInstallStatusResponse = await graphClient.DeviceManagement.Reports.GetDeviceInstallStatusReport.PostAsync( new GetDeviceInstallStatusReportPostRequestBody() { Filter = $"(ApplicationId eq '{id}')", OrderBy = new List<string>() { "DeviceId", "ApplicationId", "UserId", "DeviceName", "UserPrincipalName", "UserName", "Platform" }, Skip = skip, Top = 10000 } , cancellationToken: CancellationToken.None);

I am using NuGet Microsoft.Graph.Beta 5.34.0-preview

Contributor guide

Open the contributing guide

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 DeviceManagement.Reports.GetDeviceInstallStatusReport in Microsoft.Graph.Beta 5.34.0-preview and reproduce the paginated request using the reported Filter, OrderBy, Skip, and Top values. Compare successive pages, including requests made after creating a new graph client, and determine whether ordering is stable and items are duplicated or missed.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp
Domain
api
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.