On Thursday, September 28, 2017 at 3:30:47 AM UTC-4, Sergi Almacellas Abellana wrote:
> I must admint that I have used party_comunication and the same aproach > when party_relationship did not exist. Once having tested the new > party_relationship module, we did the switch immediately as the latter > had a lot of benefits: How did you deal with the UI problems? When a user goes to the party page for XYZ Corporation, and wants to add a salesperson for XYZ, they want to be able to do it simply--not either (1) digging down through pop-ups first for party relationship, then for a new party, and then back up to the relationship, or (2) leaving the XYZ screen to create a new party. I understand that party_relationship has a more robust data model than party_communication, but, in the trade-off between UI and flexible data model, UI sometimes should win, especially the use case does not require complex spaghetti Many2Many relationship between employees and their companies. -- 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/857cf4ef-6f8f-4d0b-9526-49e19126889e%40googlegroups.com.
