Fixed issue with file encoding in convert function

ykuijs · Jul 3, 2024 · 859ffda · 859ffda
1 parent 251abb4
commit 859ffda
Show file tree

Hide file tree

Showing 2 changed files with 6 additions and 1 deletion.
diff --git a/CHANGELOG.md b/CHANGELOG.md
@@ -5,6 +5,11 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
+### Fixed
+
+- Fixed issue in Convert-M365DSCExportToPowerShellDataFile where the created data file
+  was in ASCII format, causing special characters to be displayed incorrectly.
+
 ## [0.2.11] - 2024-06-19
 
 ### Changed

diff --git a/source/Public/Convert-M365DSCExportToPowerShellDataFile.ps1 b/source/Public/Convert-M365DSCExportToPowerShellDataFile.ps1
@@ -158,7 +158,7 @@ function Convert-M365DSCExportToPowerShellDataFile
         # Check if data is available
         if ($Obj_Result.NonNodeData.$Workload)
         {
-            $Obj_Result | ConvertTo-Expression -Depth 20 -Expand 20 | Out-File $Path_CompositeConfig -Force -Confirm:$false -Encoding ascii
+            $Obj_Result | ConvertTo-Expression -Depth 20 -Expand 20 | Out-File $Path_CompositeConfig -Force -Confirm:$false -Encoding UTF8
             'Result Composite config created: {0}' -f $Path_CompositeConfig | Write-Log
         }
         else