Incorrect parsing of a message payload's date fields inside ServiceInsight json viewer #1367
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.
Description
If a message payload has a date field, then the value of that date field changes based on the user's computer clock when viewed in ServiceInsight Json viewer.
Expected Behavior
Any data inside the message payload should not be altered while parsing .
Observed Behavior
If a message payload has a date field, then the value of that date field changes based on the user's computer clock when viewed in ServiceInsight Json viewer.
Steps to reproduce
This PR applies DateParseHandling.None to fix the datetime mismatch while parsing