microsoftgraph / microsoftgraph/msgraph-beta-sdk-dotnet
The getConfigurationPoliciesReportForDevice report request fails if orderBy is specified
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 112
- Forks
- 37
- Avg merge
- 14h 57m
- Merged PRs (30d)
- 3
Description
Describe the bug
When calling POST https://graph.microsoft.com/beta/deviceManagement/reports/getConfigurationPoliciesReportForDevice, I receive an error if specify any orderBy (I tried several combinations: ["PolicyId"], ["IntuneDeviceId"], ["IntuneDeviceId", "PolicyId"]).
However, the same request works if I just remove "orderBy" parameter
Expected behavior
Request should work with orderBy parameter
How to reproduce
Call POST https://graph.microsoft.com/beta/deviceManagement/reports/getConfigurationPoliciesReportForDevice with request body like:
{
"filter": "(IntuneDeviceId eq '') and ((PolicyBaseTypeName eq 'Microsoft.Management.Services.Api.DeviceConfiguration') or (PolicyBaseTypeName eq 'DeviceManagementConfigurationPolicy') or (PolicyBaseTypeName eq 'Microsoft.Management.Services.Api.DeviceManagementIntent') or (PolicyBaseTypeName eq 'DeviceConfigurationAdmxPolicy'))",
"orderBy": ["PolicyId"]
}
SDK Version
5.127.0
Latest version known to work for scenario above?
No response
Known Workarounds
No response
Debug output
Click to expand log
```</details>
### Configuration
_No response_
### Other information
_No response_
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.
Research direction
Start by reproducing the POST request to the documented Microsoft Graph beta endpoint using the supplied filter and orderBy values, then inspect the SDK request path for this report operation. Compare requests with and without orderBy and verify whether the failure is in the SDK or the service. Done means identifying the responsible layer and documenting or resolving the failing behavior.
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
- 35/100