Community mailing list archives
Re: Usability/design in relation to res.partnerby
Anubía, soluciones en la nube, S.L., Alejandro Santana
Just to get the picture where "fisrt name" and "last name" is not always a good approach in a worldwide environment, please, take a look at:
Also, you might find useful some community modules here:
Regarding implementation on address retrieval, surely there is room to improve.
2015-08-18 2:34 GMT+02:00 OpenERP Master <firstname.lastname@example.org>:
There are a few more pain points here, but seriously I have trouble understanding this functionality. IMO its broken.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.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.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.Why not implement ability to assign a default. This way would produce random defaults.The way addresses are retrieved seems horrendous. Can someone justify this method as is?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.Hello,I wanted to share my dissatisfaction in respect to res.partner.