fix: bom cost update is not working (backport #43155) #43156
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
![mergify[bot]](https://avatars.githubusercontent.com/in/10562?s=60&v=4){kind=small}
(cherry picked from commit 05f9015)
frappe-pr-bot
pushed a commit
that referenced
this pull request
Sep 11, 2024
# [14.74.0](v14.73.2...v14.74.0) (2024-09-11) ### Bug Fixes * `default_advance_account` field in Process Payment Reconciliation ([3691a50](3691a50)) * bom cost update is not working (backport [#43155](#43155)) ([#43156](#43156)) ([9110534](9110534)) * cancel common party advance jv while canceling the invoice ([f506952](f506952)) * check multi-currency on jv for common party accounting with foreign currency ([a3a40fe](a3a40fe)) * **Delivery Note:** translatability of validation errors ([5e33961](5e33961)) * incorrect actual cost in Procurement Tracker report (backport [#43109](#43109)) ([#43137](#43137)) ([a4b9dda](a4b9dda)) * incorrect qty after transaction in SLE (backport [#43103](#43103)) ([#43104](#43104)) ([77892f4](77892f4)) * return type of `get_party_details` (backport [#43131](#43131)) ([#43135](#43135)) ([e8aae50](e8aae50)) * set today in 'On This Date' in Available Batch Report ([36f65fc](36f65fc)) * uncomment internal parties ([4dd06b6](4dd06b6)) * unreconcile allocation child table redirect url voucher no issue ([53496ed](53496ed)) ### Features * utility report to identify invalid ledger entries ([37b8715](37b8715))
|
🎉 This PR is included in version 14.74.0 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
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.
Sometimes status remain "In Progress" for the BOM Update Log to update the cost in all BOMs and due to which users are not able to make new BOM Update Log record to update latest cost in all BOMs.
Solution
The system will wait for one day to complete the job, and if it is not completed within that time, the system will allow a new log to be made to update the latest cost in all BOMs.
This is an automatic backport of pull request #43155 done by Mergify.