fix: added fieldname to avoid fieldname to translate #44439
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
sagarvora
added
backport version-14-hotfix
This was referenced Nov 29, 2024
sagarvora
added a commit
that referenced
this pull request
Nov 29, 2024
…-44439 fix: added fieldname to avoid fieldname to translate (backport #44439)
sagarvora
added a commit
that referenced
this pull request
Nov 29, 2024
…-44439 fix: added fieldname to avoid fieldname to translate (backport #44439)
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.
Issue:
If
fieldnameis not given, it scrubs the field label. However, if the label is translated, it also translates thefieldname, which prevents data from being set in the datatable.erpnext/erpnext/accounts/report/accounts_receivable/accounts_receivable.py
Line 1134 in b800221
View Difference
Before:
After:
Important
Backport require for both
V-15andV-14