Handling deeper level (terms children) Reused Child Terms hierarchy in TermGroups Object Provisioning (only TermSet reused terms direct children hierarchies were being provisioned). #801
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
…n TermGroups Object Provisioning (only TermSet reused terms direct children hierarchies were being provisioned). Adding really sucky (temporary) way to handle transient Server Exceptions (I found no other solution for now)!
Autophanous
changed the title
|
Hi @wobba ... I'm a newbie contributor .... just wanted to check whether I should change this pull request in any way as to facilitate its processing ... |
…n TermGroups Object Provisioning (only TermSet reused terms direct children hierarchies were being provisioned). Adding really sucky (temporary) way to handle transient Server Exceptions (I found no other solution for now)!
…ous/pnpframework into HandleNestedReusedTerms
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.
Reused Terms hierarchies in deeper levels were being ignored.
Added handling for all found Reused Terms hierarchies in the processing scope.
Unfortunately, I had to add a really sucky (temporary) way to handle transient Server Exceptions (I found no other solution for now)!
Refs:
Maybe Server Exceptions should be included/handled in Microsoft.SharePoint.Client.ClientContextExtensions.ExecuteQueryRetry retry logic (currently it's just throwing the exception)