Address issue with export issue to xml #1969
Merged
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
lusassl-msft
approved these changes
Feb 7, 2024
Placed in a stop action and a try catch block. Also included a depth for ConvertTo-Json as that by default would only work 2 levels
dpaulson45
force-pushed
the
dpaul-HcExport
branch
from
8bf729f to
756c271
Compare
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.
Issue:
Described in #1412
Fix:
Placed in a stop action and a try catch block. Also included a depth for ConvertTo-Json as that by default would only work 2 levels
Resolved #1412
Validation:
Verified by placing a
throwprior to theExport-Clixmlwhen testing to make sure the logic works as expected.