Fix issue when GST number is null#2724
Merged
GeorgeWalker merged 1 commit intoJul 28, 2025
Merged
Conversation
GeorgeWalker
approved these changes
Jul 28, 2025
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Cause:
This issue is due to null values in the GST number in Dynamics. In the portal, we enforce that the user provides a value, but Dynamics might lack this validation.:
Fix:
convertSupplierGSTNumberToFormModelmethod now safely handles cases where the input GST number is null, undefined, or empty by returning an object with empty string parts, preventing runtime errors.