If you need the user id from the order object you can get it by calling order.getParentUser().getUserId() so there should be no need to have it as its own field in the order object.
Sean On Aug 14, 2:11 am, Matt Quackenbush <[email protected]> wrote: > It is indeed very common for people to attempt to use a field in both a > relationship and a property, but it still cannot be done with Transfer. > Well, at least not like that. There was a thread a really long time ago > that discussed a workaround, of sorts. > > http://groups.google.com/group/transfer-dev/browse_thread/thread/613e... > > But again, that is a workaround. What are you trying to do? If you have > the relationship declared, you already have access to everything you need > via the composed class(es). --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
