fix: Ignore rounding diff while importing JV using data import #25715
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
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.
Due to floating point arithmetic addition in python there may be cases where there is minor difference in total debit and total credit even though sum of debit and credit values is equal. Due to this user is unable to import JVs using data import.
Ignored total debit and credit validation while importing JVs
If "Submit After Import" is checked in Data Import then the JV will be submitted via Data import if diff is within permissible value else GL Entry validation for unequal debit and credit will be triggered.
If "Submit After Import" then the user can simply import the entry, fix the diff amount manually and submit