MOrderLine.setPrice should not override UnitOfMeasure
Description
This is only a bug during FitNesse testing that does not engage Callout resulting in Price been null, and while setting Price, it also sets UOM from the Product when it should first check if User has set an UOM value already.
I was testing a different 6Pack UOM and this was discovered to override with Product's base UOM which is Each.
Patch attached merely makes sure the UOM is empty before doing so.
Environment
None
Attachments
1
Activity
Carlos Ruiz
June 10, 2019 at 4:37 PM
Thanks @redhuan d. oon, I did a test to the "RePrice Order/Invoice" process and it was destroying the UOM of order lines because of the same code.
This is only a bug during FitNesse testing that does not engage Callout resulting in Price been null, and while setting Price, it also sets UOM from the Product when it should first check if User has set an UOM value already.
I was testing a different 6Pack UOM and this was discovered to override with Product's base UOM which is Each.
Patch attached merely makes sure the UOM is empty before doing so.