fix: use highest precision for exchange rate. #33275
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
dj12djdjs
requested review from
nextchamp-saqib,
deepeshgarg007 and
ruthra-kumar
as code owners
|
@Mergifyio backport version-14-hotfix |
✅ Backports have been created
|
deepeshgarg007
added a commit
that referenced
this pull request
Dec 16, 2022
…-33275 fix: use highest precision for exchange rate. (backport #33275)
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Update payment entry exchange rate fields to use highest precision setting.
This is to follow the same convention as:
Sales Invoice:erpnext/erpnext/accounts/doctype/sales_invoice/sales_invoice.json
Line 615 in 7d41f63
Purchase Invoice:erpnext/erpnext/accounts/doctype/purchase_invoice/purchase_invoice.json
Line 492 in 7d41f63