Fix: preserve non-ASCII characters in spo-request-pnp-reindex-user-profile (#878)#964
Open
juandresrodca wants to merge 1 commit into
Open
Fix: preserve non-ASCII characters in spo-request-pnp-reindex-user-profile (#878)#964juandresrodca wants to merge 1 commit into
juandresrodca wants to merge 1 commit into
Conversation
Set-Content defaulted to ANSI encoding, corrupting non-ASCII characters (ä, ö, ü, ñ) in the Department field before the JSON batch file was uploaded to the UPA bulk import job. Add -Encoding UTF8 so the import preserves the original characters. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Fixes #878. The reindex script wrote its JSON batch file with
Set-Contentand no-Encoding, which defaults to ANSI on Windows PowerShell. Non-ASCII characters in the Department field were therefore corrupted before the file was uploaded to the UPA bulk-import job.Change
Added
-Encoding UTF8to theSet-Contentcall so the import preserves the original characters.This matches the fix validated by @DavorSukeri in the issue thread.