c2c-oerpscenario team mailing list archive

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

@sraps: 
Thanks for summing up your requirements. Unfortunately, I still don't see a valid reason for keeping this bug open based on your list. The bottom-line is basically that the 'code' field has been renamed to 'name', so it's not actually gone missing.

>From your list, here is what I understand:

1) You think a translatable label is needed, which is what I was not
sure about. The old "name" was removed to avoid confusion, but it was
not translatable. Do you have some real use cases where having such a
label would be really *required*, and thus worth it? Most people are
familiar with currency ISO codes nowadays, and as you want these to be
printed everywhere, I suppose you expect end-users to be able to
understand them too... In any case, this does sound like a debatable
wishlist, as others have pointed out.

2) The name of the field was chosen according to conventions, and this cannot be called a bug. If anything, this change just makes it more obvious that currencies should only be referred to by their ISO codes in all circumstances, as you pointed out.
Also, changing the database schema is not allowed in point-releases, so this can only be considered as wishlist for 6.1. 

3),4),5),6) Nothing changed in 6.0 about these points, as far as I know.
Shouldn't these be different wishlists, or suggestions on
feedback.openerp.com where the community can vote about them?

Now, I totally understand that you would like to have been asked your opinion on this change beforehand, and this change probably deserved it. I will spread the word again internally about discussing such changes with the community.
However, if you think about it for a minute, the change was limited to renaming a column and removing one that was not used in any critical place (the label, which used to hold a copy of the code in many cases). Not the typical world-breaking change.
Note that you should also join the openerp-expert-accounting mailing-list where such propositions are likely to be discussed. This is one of the places where professional tax consultants can make a difference.

To conclude, I think you understand that there is no "code" field in
res.currency in v6.0 anymore, not because it was removed but because it
was simply renamed "name", so no bug there.

Thanks for bringing the other issues to our attention, too.

-- 
You received this bug notification because you are a member of C2C
OERPScenario, which is subscribed to the OpenERP Project Group.
https://bugs.launchpad.net/bugs/709201

Title:
  No "code" field in "res.currency" object

Status in Aeroo Reports for Open ERP:
  Confirmed
Status in OpenERP Modules (addons):
  Confirmed
Status in OpenOffice.org Reporting Engine for OpenObject:
  Confirmed

Bug description:
  There is no code field in the res.currency object, which used to hold
  ISO 4217 (http://en.wikipedia.org/wiki/ISO_4217) code for the
  currency. ISO code is the only referable code for a currency, any
  other name is just user friendly representation and may vary from
  country to country, still they are not official names of the currency.

  Please do not disregard this defect as many modules depend on this
  code do find correct currency in a system.

  This defect is present in whole OpenERP's 6th version branch.