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

Set Sales Order Line's ProductDescription as Product BOM's description #4535

Closed
teosarca opened this issue Aug 30, 2018 · 2 comments
Closed

Comments

@teosarca
Copy link
Member

teosarca commented Aug 30, 2018

Is this a bug or feature request?

Feature

What is the current behavior?

Which are the steps to reproduce?

What is the expected or desired behavior?

When entering a product which is BOM the C_OrderLine.ProductDescription shall be set from BOM description.
i.e. one line for each BOM Line:

ProductValue ProductName Qty UOM

This feature shall be switchable on/off using a sysconfig.

Also make sure the ProductDescription is visible in sales order document print (jasper).

@teosarca teosarca self-assigned this Aug 30, 2018
@teosarca teosarca changed the title Set Sales Order Line's Description as Product BOM's description Set Sales Order Line's ProductDescription as Product BOM's description Aug 30, 2018
@metas-dh
Copy link
Member

metas-dh commented Aug 31, 2018

Results of IT1
tested in mf15

  1. feature shall be switchable on/off using a sysconfig: OK
  2. C_OrderLine.ProductDescription shall be set from BOM description: OK
  3. one line for each BOM Line:
  • ``ProductValue ProductName Qty UOM` : Qty UOM is set as qty %, when the BOM is set like that, OK?

2018-08-31 11_29_22-metasfresh

  • in orderline, all products from BOM are shown in 1 line, but displayed with multiline (1 line per product) when you mouse over: OK i think? (i did not set the field to multiline text myself for testing)
  • multiline display when you doubleclick in the field, with scrollbar, and editable: OK
  1. ProductDescription is visible in sales order document print (jasper): OK

2018-08-31 11_30_15-143_0016 pdf

  1. question / problem:
  • ProductDescription is not shown in the advanced edit of C_OrderLine; i added the checkbox for IsIndividualDescription so it would be displayed if IsIndividualDescription=Y , but:
    when you set IsIndividualDescription=Y , ProductDescription in the advanced edit is empty, and the ProductDescription already set from BOM description in grid view, is set back and now empty as well:

grid view:
2018-08-31 11_29_22-metasfresh

advanced edit, after setting IsIndividualDescription=Y:
2018-08-31 11_38_13-metasfresh

back in grid view:
2018-08-31 11_38_29-metasfresh

  • same goes for Add new : when you set IsIndividualDescription=Y , ProductDescription is empty and will not be shown in the orderline grid view; when you leave IsIndividualDescription=N the ProductDescription in orderline grid view shows the BOM Description

=> not sure if this is a problem, i.e. if customers will use this feature and also use Advanced edit / Add new ? @metas-mk, @teosarca: wdyt?

metas-ts added a commit that referenced this issue Sep 3, 2018
[#4475](#4475) Refund contract - add further options
[#4511](#4511) Implement support for MSV3 version 1
[#4530](#4530) WebUI Adjustments for Country, Postal and City Window
[#4535](#4535) Set Sales Order Line's ProductDescription as Product BOM's description
[#4536](#4536) Introduce AD_Table.IsEnableRemoteCacheInvalidation
[#1032](metasfresh/metasfresh-webui-api-legacy#1032) Window layout API shall provide text multilineText and multilineTextLines properties
[#4526](#4526) Filter for attributes in picking terminal shall be set by default
  * [#4537](#4537) Invoice candiate handler BL creates lock with non-unique owner
  * [#438](metasfresh/metasfresh-webui-api-legacy#438) minor: error for wizard with no picture
@metas-dh
Copy link
Member

checked with metas-mk: OK, rolled out at customer, working fine.

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