You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Details of the scenario you tried and the problem that is occurring
When running Update-M365DSCResourceDocumentationPage the resource IntuneSettingCatalogCustomPolicyWindows10 fails since the schema has one empty CIMInstance and this makes the cmdlet fail, see below
Verbose logs showing the problem
Get-DscResourceSchemaPropertyContent : Cannot bind argument to parameter 'Property' because it is null.
At C:\Users\ptmestrer\Documents\GitHub\Microsoft365DSC\Modules\Microsoft365DSC\Modules\M365DSCDocGenerator.psm1:597 char:83+ ... rceSchemaPropertyContent -Property $embeddedSchema.Attributes-UseMar ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : InvalidData: (:) [Get-DscResourceSchemaPropertyContent], ParameterBindingValidationException
+ FullyQualifiedErrorId : ParameterArgumentValidationErrorNullNotAllowed,Get-DscResourceSchemaPropertyContent
Suggested solution to the issue
Add missing properties to schema
The DSC configuration that is used to reproduce the issue (as detailed as possible)
N/A
The operating system the target node is running
Win10
Version of the DSC module that was used ('dev' if using current dev branch)
1.23.510.1
The text was updated successfully, but these errors were encountered:
Details of the scenario you tried and the problem that is occurring
When running Update-M365DSCResourceDocumentationPage the resource IntuneSettingCatalogCustomPolicyWindows10 fails since the schema has one empty CIMInstance and this makes the cmdlet fail, see below
Verbose logs showing the problem
Suggested solution to the issue
Add missing properties to schema
The DSC configuration that is used to reproduce the issue (as detailed as possible)
N/A
The operating system the target node is running
Win10
Version of the DSC module that was used ('dev' if using current dev branch)
1.23.510.1
The text was updated successfully, but these errors were encountered: