Hi Matt! Actually, trying to save the object PersonOrg still throws a "duplicate column name" error :( I thought that it was fixed because I configured a copy of the original object "PersonOrgPlain" in transfer.xml with no relation to Person or Org, and was saving this kind of object.
What works better is the view of the Person page with the list of related Orgs and Projects. I guess there's no way of saving objects that are the end of a o2m relation, because they will always have an extra foreignKeyId field... I'd like to have all the relationship Object's data management within the same configuration, but I can live with duplicating the objects that deal with m2m relations for now... I'd like to find a more elegant solution, from the data model's design and coding perspective though. Any suggestions apart from overwriting the generated methods in the PersonOrg objects? TIA, Pedro. --~--~---------~--~----~------------~-------~--~----~ Before posting questions to the group please read: http://groups.google.com/group/transfer-dev/web/how-to-ask-support-questions-on-transfer You received this message because you are subscribed to the Google Groups "transfer-dev" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/transfer-dev?hl=en -~----------~----~----~----~------~----~------~--~---
