microsoftgraph / microsoftgraph/msgraph-metadata

MgDeviceManagementDeviceCompliancePolicy Many "No OData route exists that match template" error

Open
#245 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

metadata-issue priority:p2
Dominant language
XSLT
Stars
166
Forks
55
Avg merge
16h 12m
Merged PRs (30d)
14

Description

If I try
Get-MgDeviceManagementDeviceCompliancePolicy -DeviceCompliancePolicyId $deviceCompliancePolicyId
work well, but if I launch
Get-MgDeviceManagementDeviceCompliancePolicyScheduledActionForRule -DeviceCompliancePolicyId $deviceCompliancePolicyId
or
New-MgDeviceManagementDeviceCompliancePolicyScheduledActionForRule -DeviceCompliancePolicyId $deviceCompliancePolicyId -RuleName "Test"
or
Update-MgDeviceManagementDeviceCompliancePolicyScheduledActionForRuleScheduledActionConfiguration
I always get the same error
No OData route exists that match template

2023-01-03_17h07_02

Update-MgDeviceManagementDeviceCompliancePolicyScheduledActionForRuleScheduledActionConfiguration error:

2023-01-03_17h12_25

NB To retrieve the correct IDs above I use the graph API in this way:

2023-01-03_17h14_24

The same problem there is if Run in Microsoft Graph the same function:

2023-01-03_17h10_14

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 failing Get-, New-, and Update-MgDeviceManagementDeviceCompliancePolicyScheduledActionForRule commands and compare their routes with the successful Get-MgDeviceManagementDeviceCompliancePolicy call. Inspect the corresponding Microsoft Graph requests and repository metadata to identify the route mismatch; done means the affected operations no longer return “No OData route exists that match template.”

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.