We use the trytonspain's party_communication module, which basically uses Addresses to model individuals associated with the Party, and makes Contact Mechanism many2one on Addresses. (party_relationship may be the more recommended solution, but we found it not as helpful.)
Now we want to be able to move Addresses from one Party to another. Digging into the Party module, there is an odd implementation for preventing changing an Address's, or Contact Mechanism's, Party. Instead of just making the field readonly, there are UserError calls in overwritten write methods.[1] If this a legacy implementation (something that today would just be handled with readonly)? Is anyone aware of traps lurking if I allow change of the Addresses' party field (by making it read/write and removing the hooks in the overridden write methods)? (This would also involve overloading Address's write to ensure that all of the Address's Contact Mechanisms move along with it.) [1] http://hg.tryton.org/modules/party/file/3.4/address.py#l158 http://hg.tryton.org/modules/party/file/3.4/contact_mechanism.py#l87 Any insights would be greatly appreciated. -- You received this message because you are subscribed to the Google Groups "tryton" group. To view this discussion on the web visit https://groups.google.com/d/msgid/tryton/5c74e459-025c-4a15-98be-36f6576e1734%40googlegroups.com.
