Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: Skip empty rows while updating unsaved BOM cost (backport #28136) #28142

Merged
merged 1 commit into from
Oct 29, 2021

Conversation

mergify[bot]
Copy link
Contributor

@mergify mergify bot commented Oct 29, 2021

This is an automatic backport of pull request #28136 done by Mergify.


Mergify commands and options

More conditions and actions can be found in the documentation.

You can also trigger Mergify actions by commenting on this pull request:

  • @Mergifyio refresh will re-evaluate the rules
  • @Mergifyio rebase will rebase this PR on its base branch
  • @Mergifyio update will merge the base branch into this PR
  • @Mergifyio backport <destination> will backport this PR on <destination> branch

Additionally, on Mergify dashboard you can:

  • look at your merge queues
  • generate the Mergify configuration with the config editor.

Finally, you can contact us on https://mergify.io/

- Dont try to get valuation rate if row has no item code
- Dont try to add exploded items if row has no item code

(cherry picked from commit 292419b)
@ankush ankush merged commit 1454f8b into version-13-hotfix Oct 29, 2021
@mergify mergify bot deleted the mergify/bp/version-13-hotfix/pr-28136 branch October 29, 2021 08:49
asoral pushed a commit to asoral/erpnext that referenced this pull request Nov 12, 2021
…rappe#28142)

- Dont try to get valuation rate if row has no item code
- Dont try to add exploded items if row has no item code

(cherry picked from commit 292419b)

Co-authored-by: Marica <maricadsouza221197@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants