c2c-oerpscenario team mailing list archive

["Olivier Dony \(OpenERP\)" <619239@xxxxxxxxxxxxxxxxxx>]

Hello Michael,

I will convert this bug into a question (which will incidentally mark it
as Invalid), because as you've seen it may become a FAQ.

Basically what you are seeing is normal, albeit not very intuitive, and
is a consequence of the multi-language features in OpenERP. A longer
explanation follows below, similar to what Borja tried to explain
already. Note that however the other issues you are mentioning (such as
the date format not being applied for en_US) do deserve separate bug
reports, as these seem to be real bugs we should fix.

***

Everything in OpenERP uses "international/american" english by default, and as soon as you install another language (even en_GB) you turn on the multilingual features.
One of these features is the fact that certain field can be marked as being "translatable" (as shown by the flag icon in GTK client), when it makes sense to provide translated values for them. One famous example is the name of products, but there are others. This is useful because OpenERP can then use the appropriate translated values, for example when printing documents containing these values for foreign customers.

When you create a product with only en_US installed, OpenERP stores this:
    displayed value for ID1: Product 11111 (en_US)
    product table:  ID1: Product 11111 (en_US)
    translations: /

If you install an additional language like en_GB and select it in your user preferences, and create a product, here is what happens instead (OpenERP copies the value to all translations, as there is no better value):
    displayed value for ID1: Product 11111 (en_GB)
    product table:  ID1: Product 11111 (en_US)
    translations: ID1: Product 11111 (en_GB)

When you later duplicate this product, the system must duplicate all information and translated values, so you end up with:
    displayed value for ID1: Product 11111 (en_GB)
    displayed value for ID2: Product 11111 (en_GB)
    product table:  ID1: Product 11111 (en_US)
    product table:  ID2: Product 11111 (en_US)
    translations: ID1: Product 11111 (en_GB)
    translations: ID2: Product 11111 (en_GB)

When you later edit the Product Name after the duplication, you are only modifying the displayed value (depending on your preferred language), but the other translations are left untouched (the system cannot guess how to update the translations, it needs to be done manually), so you end up with this:
    displayed value for ID1: Product 11111 (en_GB)
    displayed value for ID2: Product 22222 (en_GB)
    product table:  ID1: Product 11111 (en_US)
    product table:  ID2: Product 11111 (en_US)
    translations: ID1: Product 11111 (en_GB)
    translations: ID2: Product 22222 (en_GB)

As you can see, the new product still has the en_US name of the initial product, which means that it may appear with the wrong name depending on the context! 
This also affects search results as search is looking up values in all tables: product table + translations!

Solution: you simply need to set the translated values manually on the
new product, e.g. by clicking on the flag icon next to its name.

Summary: users of multi-language OpenERP systems need to be extra
careful when duplicating products (or any document with translatable
fields), and make sure to edit all translations of these fields when
modifying them.

We are aware that this is a usability problem, and are looking for ideas
to improve this in future versions of OpenERP, while preserving the
translation features. Suggestions are welcome :-)

-- 
Product duplication seems to confuse original product name with new copy
https://bugs.launchpad.net/bugs/619239
You received this bug notification because you are a member of C2C
OERPScenario, which is subscribed to the OpenERP Project Group.

Status in OpenObject Server: Invalid

Bug description:
When you duplicate a product using: Form->duplicate it will not duplicate the product correctly.
The description still seems linked between the original and duplicate when creating the purchase order
EG.
create product with Name:11111  Code: 11111
Duplicate product changing Name to: 22222 and Code: 22222

Create purchase order and add new products:
product search for: 11111. 
Result will return 11111 and 22222. (INCORRECT)

Now when you add product 22222 to purchase order it will have a description of 11111 (INCORRECT)

Duplicating a product is often used as you do not have to re-input all the data for a similar product.
I also do not know what the effect is on other processes downstream. Eg. journals, MRP, etc..
I would assume that this process is used often and would need to be looked at.