Generated HTML from asserting blueprint does not contain all the variables from the blueprint #4516
Labels
Comments
dosLL
changed the title
|
Could you run a test with the latest release? We updated DSCParser with the first April release and this should improve the reports |
|
I tried the assert with the new version - no change. If you need any more infos, let me know. Edit: I removed the values that got queried from the blueprint, ran it and ended up with a html without any values. |
|
The Update to the DSCParser seems to have changed something. Atleast I'm getting a Error Message with the -verbose parameter. Error appears after all the data is collected and the html should be generated. TerminatingError(Write-Progress): "Cannot validate argument on parameter 'PercentComplete'. The 101 argument is greater than the maximum allowed range of 100. Supply an argument that is less than or equal to 100 and then try the command again."
Write-Progress : Cannot validate argument on parameter 'PercentComplete'. The 101 argument is greater than the maximum
allowed range of 100. Supply an argument that is less than or equal to 100 and then try the command again.
At C:\Program Files (x86)\WindowsPowerShell\Modules\DSCParser\2.0.0.3\Modules\DSCParser.psm1:28 char:41
+ -PercentComplete $percent
+ ~~~~~~~~
+ CategoryInfo : InvalidData: (:) [Write-Progress], ParameterBindingValidationException
+ FullyQualifiedErrorId : ParameterArgumentValidationError,Microsoft.PowerShell.Commands.WriteProgressCommand
Write-Progress : Cannot validate argument on parameter 'PercentComplete'. The 101 argument is greater than the maximum
allowed range of 100. Supply an argument that is less than or equal to 100 and then try the command again.
At C:\Program Files (x86)\WindowsPowerShell\Modules\DSCParser\2.0.0.3\Modules\DSCParser.psm1:28 char:41
+ -PercentComplete $percent
+ ~~~~~~~~
+ CategoryInfo : InvalidData: (:) [Write-Progress], ParameterBindingValidationException
+ FullyQualifiedErrorId : ParameterArgumentValidationError,Microsoft.PowerShell.Commands.WriteProgressCommand |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi.
when asserting a blueprint with the following command:
Assert-M365DSCBlueprint -BluePrintUrl <path to blueprint> -OutputReportPath <path to html> -Credentials $credentialthe generated html does not contain all of the variables defined in the blueprint.
Blueprint looks like the following (contains about 144 variables to check):
HTML looks like this:
There are about 50% of the needed variables missing. I do not understand why. Verbose Output is not showing any errors.
Did I do something wrong?
Thank you for your help!
The text was updated successfully, but these errors were encountered: