Bogus translations of field names break interactivity on bank account

[Numérigraphe]

In bank accounts, the fields are dynamically made read-only/read-write and required/optional, based res.partner.bank.type.field records.
These records have a translatable name, but changing the en_US name will break the UI interactivity.

So it should be made clear that it must not be changed, by adding a help text and making this field untranslatable.

Lionel.

[Numérigraphe (numerigraphe)]

It would be even better if the interactivity would be based on XML ids and not names...
Lionel.

[Amit Parik (amit-parik)]

Hello,

I have checked your issue with bogus translation but I didn't face any problem at my end,

I have attached the video for your more reference , So would you please check it and notify us.

Thanks and waiting for your reply!

[Numérigraphe (numerigraphe)]

"changing the en_US name will break the UI interactivity."
Have you tried that?
Lionel

[Amit Parik (amit-parik)]

Hello Lionel,

Yes, We have tried it and I have also checked it one more time.

Most important thing is attrs/domian is based on Bank type 's code field not its name field.

Thanks!

[Numérigraphe (numerigraphe)]

I'm reopening this bug, though I'm not sure what to do.
1/ Clearly you did not understand the bug report. It's about the English name of the *fields*, not that of the types.
2/ I'm not sure those names can still be changed using the default views in v7.0 or trunk - but anyway it still affects people upgrading from v6.0/6.1.

The right way to fix this would be to add a "code" column in fields, and use that instead of the field's name when building the UI.

Lionel Sausin.

[Amit Parik (amit-parik)]

Hello Lionel,

As per our bug management policy we are not consider bug report of last stable version. If you want this on v6.1 then you have to contact our OPW team at <email address hidden>.

Thank you!