Comment 43 for bug 1160365

And Now...

My friend is so funny you lose the fight, with your own argument, and i think you must rectify, or explain us, how do i make this approach.

The SAGE thing you show:

http://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

See you have 2 relations with what we have now called "Res Partner"

Client:
Address Expedition :

We need Exactly this in V7.0 how do we solve that without contact_id?

Sorry dude, if you know ALL the work it represent in our 3 localizations and in our 4 parallel deployments, you should feel like me.

I hope you think better the situation and the solution.

Important:

This __are__ not computed fields, the must be coded and saved....

And from an accounting Point of View, we need both references in account move line, exactly as we had before __or better__.....

Help me to see your point my friend Pleaseeee.!!!

Regards.