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
This is an example of the Excel output. You can see that the column 'Value' does not contain the actual values, but the text 'System.Collections.Specialized.OrderedDictionary'
This issue is very likely not limited to the resources/components mentioned abour, so other resources may have the same issue.
It may well be that not only the Excel export is affected, but also other exports and other M365DSC features relying on the ps1 file created during the initial export.
Verbose logs showing the problem
See above.
Suggested solution to the issue
Change the export code, so that the dictionary object is resolved to the actual values.
The DSC configuration that is used to reproduce the issue (as detailed as possible)
Version of the DSC module that was used ('dev' if using current dev branch)
1.23.405.1, 1.23.412.1
The text was updated successfully, but these errors were encountered:
GruberMarkus
changed the title
Multiple resources: Excel export does not resolve values, shows "System.Collections.Specialized.OrderedDictionary" insted
Multiple resources: Excel export does not resolve values, shows "System.Collections.Specialized.OrderedDictionary" instead
Apr 18, 2023
Details of the scenario you tried and the problem that is occurring
This is an example of the Excel output. You can see that the column 'Value' does not contain the actual values, but the text 'System.Collections.Specialized.OrderedDictionary'
This issue is very likely not limited to the resources/components mentioned abour, so other resources may have the same issue.
It may well be that not only the Excel export is affected, but also other exports and other M365DSC features relying on the ps1 file created during the initial export.
Verbose logs showing the problem
See above.
Suggested solution to the issue
Change the export code, so that the dictionary object is resolved to the actual values.
The DSC configuration that is used to reproduce the issue (as detailed as possible)
Can be reproduced with any export
The operating system the target node is running
OsName : Microsoft Windows 10 Enterprise
OsOperatingSystemSKU : EnterpriseEdition
OsArchitecture : 64-Bit
WindowsVersion : 2009
WindowsBuildLabEx : 19041.1.amd64fre.vb_release.191206-1406
OsLanguage : de-DE
OsMuiLanguages : {de-DE}
Version of the DSC module that was used ('dev' if using current dev branch)
1.23.405.1, 1.23.412.1
The text was updated successfully, but these errors were encountered: