Community mailing list archives

community@mail.odoo.com

Re: Usability/design in relation to res.partner

by
OpenERP Master
- 08/17/2015 20:36:17
I created a very simple method that im sure people will hate and it adds more db calls, but the functionality provided is much better.

https://gist.github.com/aliomattux/566d2e319fca94a1febf

On Mon, Aug 17, 2015 at 7:27 PM, OpenERP Master <openerpmaster@gmail.com> wrote:
Hello,

I wanted to share my dissatisfaction in respect to res.partner.

Why is there not a firstname, lastname field. This is very standard in a lot of software, It is important to have them separate, especially when working with external software that require these fields independently. You end up having to do something stupid like separate on spaces which doesnt work well.

The way addresses are retrieved seems horrendous. Can someone justify this method as is?
https://github.com/odoo/odoo/blob/8.0/openerp/addons/base/res/res_partner.py#L735

Why not implement ability to assign a default. This way would produce random defaults.
Also, in onchange_partner_id in sale module, it does a select for [contact, delivery, invoice], but it does not work correctly. It always selects the partner id as invoice and delivery if the only address type available is contact. Contact addresses are not populated unless you select them.

In sale module when selecting invoice/delivery address there is no filtering based on the selected partner. It shows all partners. You would allow business users to select accidentally an address that does not even belong to the person you are billing/shipping goods. There may be a case to allow this, but probably most b2c users would not want to allow this.

In base partner view the contact view is embedded inside the partner default form view. If you want to customize this very important view, you make it more difficult than it has to be.

There are a few more pain points here, but seriously I have trouble understanding this functionality. IMO its broken.