After testing the 2 solutions provided by rvalyi and odony, we vote for rvalyi's solution for backward compatibility.
@ Fabien
We think that the OpenERP project has reached a critical mass of users and integrators in its lifecycle where those big changes should be discussed with Gold Partners and/or Community Reviewers during OpenERP Community Days. Your baby has grown and you need to give him some space to continue growing.
You were able to do that couple years ago, but there is now 3000+ modules and lots of people depending on them. Those people built and used those 3000+ modules based on the assumption that documents requiring 2 fields used partner_id and contact_id. You cannot change this assumption on your own. It generates frustration on both sides.
I think you have a great opportunity today to decide how and with who you want to build the future of OpenERP. I think the community is ready and well-structured to help you.
After testing the 2 solutions provided by rvalyi and odony, we vote for rvalyi's solution for backward compatibility.
@ Fabien
We think that the OpenERP project has reached a critical mass of users and integrators in its lifecycle where those big changes should be discussed with Gold Partners and/or Community Reviewers during OpenERP Community Days. Your baby has grown and you need to give him some space to continue growing.
You were able to do that couple years ago, but there is now 3000+ modules and lots of people depending on them. Those people built and used those 3000+ modules based on the assumption that documents requiring 2 fields used partner_id and contact_id. You cannot change this assumption on your own. It generates frustration on both sides.
I think you have a great opportunity today to decide how and with who you want to build the future of OpenERP. I think the community is ready and well-structured to help you.