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

uom in customer return lines #2399

Closed
metas-lc opened this issue Sep 8, 2017 · 2 comments
Closed

uom in customer return lines #2399

metas-lc opened this issue Sep 8, 2017 · 2 comments

Comments

@metas-lc
Copy link
Contributor

metas-lc commented Sep 8, 2017

Is this a bug or feature request?

bug

What is the current behavior?

uom piece is set by default when you want to create a new line, even if the product is on kg

Which are the steps to reproduce?

  1. go to customer return window and create a new one
    https://w101.metasfresh.com:8443/window/53097
  2. add all mandatory fields, doctype Kundenwarenrückgabe
  3. add a line with a kg product (topinambour), add HUs
    =>
    Error: Ihr Test hat einen...
    Server error
    Ihr Test hat einen bisher unentdeckten Fehler offengelegt.
    Bitte leiten Sie diese Meldung an metas weiter: Error: Failed to convert Qty=10.000000000000 of product=P002748 from UOM=Kilogramm to UOM=Stück

What is the expected or desired behavior?

we need a callout that when you add a product, the uom to be set directly, accordingly

@metas-lc metas-lc added this to the Backlog milestone Sep 8, 2017
teosarca added a commit that referenced this issue Sep 8, 2017
applies to customer/vendor receipt/shipment/return
#2399
metas-ts pushed a commit that referenced this issue Sep 8, 2017
applies to customer/vendor receipt/shipment/return
#2399

(cherry picked from commit 5a9e9a8)
@metas-ts
Copy link
Member

metas-ts commented Sep 8, 2017

cherry-picked to branch 2019-01-12

@metas-lc
Copy link
Contributor Author

IT
tested the testcase above in both swing and webui => works fine, the uom is set accordingly to product's uom OK

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants