Hotfix for Issue 4808 #4811
Open
Hotfix for Issue 4808 #4811
Conversation
This file contains 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
…sly you have to convert guid object to string first)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Type
Related Issues?
Fixes #4808
What is in this Pull Request ?
Currently
Set-PnPListItemdoesn't support term guid object for single taxonomy field, you have to convert it ToString() first, otherwise it cannot recognize it is guid and will try to run it as term path.This is due to "
value as string" cannot convert guid object to string, it will get null value. So I changed it to "value?.ToString()", the same one when handle multiple taxonomy field.