Fixed issue with Guid values not being supported for "TaxonomyFieldType" fields in batch scenarios (Set-PnPListItem, Add-PnPListItem) #5174
+62
−93
Conversation
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
…pe" fields in batch scenarios (Set-PnPListItem, Add-PnPListItem) Unified handling of input values for taxonomy items when using batch.
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.
Type
What is in this Pull Request ?
Fixed the following issues for fields of type TaxonomyFieldType for Add/Set-PnPListItem command when used in a batch scenario:
This already worked previously for fields of type TaxonomyFieldTypeMulti therefor I extracted the code for both variants to a single additional helper function so that both share the same code now.