Orderby probably does not work in DeviceManagement.Reports.GetDeviceInstallStatusReport
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 30/100
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.
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
- Dominant language
- C#
- Stars
- 112
- Forks
- 37
- Avg merge
- 14h 57m
- Merged PRs (30d)
- 3
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from microsoftgraph/msgraph-beta-sdk-dotnet
-
status:waiting-for-triage type:feature
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
-
status:waiting-for-triage type:bug
Difficulty 4/5 3-5 days Newbie friendliness 42/100
-
status:waiting-for-triage type:bug
Difficulty 4/5 3-5 days Newbie friendliness 35/100
microsoftgraph/msgraph-beta-sdk-dotnet#1155 · 1 comment ·
-
status:waiting-for-triage type:feature
Difficulty 4/5 3-5 days Newbie friendliness 45/100
microsoftgraph/msgraph-beta-sdk-dotnet#1129 · 1 reaction ·
-
.NET
Difficulty 3/5 1-2 days Newbie friendliness 25/100
All issues in microsoftgraph/msgraph-beta-sdk-dotnet
Similar issues
-
type/automation type/tech-debt
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
t/bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
ci-failure-cause test-failure
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
area:auth FE mvp P3
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
klasolsson81/jobbliggaren#1788 ·