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 : suplier order Label product must be keep on detail line #14997

Closed
wants to merge 3 commits into from

Conversation

defrance
Copy link
Contributor

FIX on supplier order the product label is not keep on detail line of order, we use continually the label of the product table.
Or if we change it (on product table) it will not change on supplier order detail

defrance and others added 3 commits October 12, 2020 17:51
Actually we use label from product but if we change it on product it will not change on the order
@@ -3368,7 +3375,8 @@ public function fetch($rowid)
$sql .= ' cd.remise, cd.remise_percent, cd.subprice,';
$sql .= ' cd.info_bits, cd.total_ht, cd.total_tva, cd.total_ttc,';
$sql .= ' cd.total_localtax1, cd.total_localtax2,';
$sql .= ' p.ref as product_ref, p.label as product_label, p.description as product_desc,';
$sql .= ' cd.label,';
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This column "label" on line level has been deprecated a long time ago.
The line of products contains a description or a product, and label of product come from the table product.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes but it's not a good way : if we change the label of the product, it must doesn't change on the supplier order (same thing on the supplier bill)
on the supplier proposal we have the label on the line level and it's a good thing

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

When the reference (id) is the same, changing the label must change the label everywhere. This is the goal of couple ref / label. If ref (primary key) point to a record, changing property for example to fix a typo error, will be visible on all document that point to it. It is the reference that define that it is same or another product, not the label.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

NO !!!!!!
the wording of a generated and transmitted document should never change, even if there is a spelling error.
If you order something from a supplier, and you change the wording of your order there could be a huge dispute.

Non, le libellé d'un document généré et transmis ne dois jamais changer, meme si il y a une faute d'orthographe.
Si tu commandes quelque chose à un fournisseur, et que tu change le libellé de ta commande il peu y avoir un énorme litige.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Allowing this sort of thing is a monstrous functional error

Copy link
Member

@eldy eldy Feb 21, 2021

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is true for a description or a ref, less for a short label. By definition a short label is just a clear text of a reference (it is even a different value for each language).
And if you duplicate data for a short label, why not doing it also for the reference (more important than the short label, the width, heigth, size of product). We can duplicate any fields of product into the line of objects but if there is one field that is less important to duplicate than reference, size, width, color, description, and intrasec characteristics of products, it is surely the short label of a product reference that does not contains any characteristics information (this default label is even not used in most cases in multi-language context).

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

the subject for me is to have the same operation whether for the parts on the customer side as for the parts on the supplier side
OR the proposals (customers and suppliers) work as well but not the orders and invoices: for the customer part we keep the wording on the line but not for the supplier part

--

le sujet pour moi c'est d'avoir le même fonctionnement que ce soit pour les pièces coté clients que pour les pièces coté fournisseurs
OR les propositions (clientes et fournisseurs) fonctionnent ainsi mais pas les commandes et les factures : pour la partie client on conserve le libellé sur la ligne mais pas pour la partie fournisseur

@eldy eldy added the PR not qualified PR is not qualified (feature not enough requested, duplicate feature or other reason) label Jan 11, 2021
@eldy
Copy link
Member

eldy commented Apr 7, 2022

PR seems it introduces more problems than it solves, so request is closed.
Note: label on lines seems no more used whatever is the object.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
PR not qualified PR is not qualified (feature not enough requested, duplicate feature or other reason)
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants