Having 1 field displayed on the GUI does not means that you do not have 2
fields stored.
Your screenshots have neither no indication if they allow to mix partners
and contacts.
If you read correctly the Raphaël's posts, you will see that he does not
say that you need to display 2 fields. You can still display only 1.
But we have to ensure that the partner_id is always a partner and not
sometimes a partner and sometimes a contact.
On Tue, Apr 9, 2013 at 9:41 AM, Fabien (Open ERP) <email address hidden> wrote:
> www.axonware. ie/catalog/ images/ quickbooks- invoice. jpg na.sage. com/sage- payment- solutions/ products- services/ sage-50- ca-fr/~ /media/ site/sage% 20payment% 20solutions/ images/ landingpages/ ssa/ss_ 2_choose_ method_ fr.jpg dynamicsgphelp. com/wp- uploads/ 2011/06/ SalesTransactio nEntry. png
> Let's have a look at the most used accounting software in the world.
> They all have only one contact/address for the invoicing. They do not
> have two fields on each document!
>
> Sometimes, optionally, they have another field for the delivery address.
> (which is another purpose)
>
> - Quickbooks (94.2% of the market share in U.S. !):
> http://
> - Sage:
>
> http://
> - Microsoft Dynamics:
>
> http://
> content/
>
> If the most used accounting software in the world do that, they can not
> all be wrong.
Having 1 field displayed on the GUI does not means that you do not have 2
fields stored.
Your screenshots have neither no indication if they allow to mix partners
and contacts.
If you read correctly the Raphaël's posts, you will see that he does not
say that you need to display 2 fields. You can still display only 1.
But we have to ensure that the partner_id is always a partner and not
sometimes a partner and sometimes a contact.