Hi,
there are several ways to do that.
just a little clarification first: if you have a UserCompany intermediate table, then it means a user can theoretically be related several companies, right? Otherwise the best design would be a single relation between User and Company.
Anyway, it does not change how to proceed.
First, as you may have noticed, you can access entity and entitycollection properties from inside your entities, corresponding to your entity's relations. You can use them to set the relations between your entities (will update the corresponding foreign keys automatically) and access the related entities' properties.
Now if you only fetch your user, the usercompany and company inner collection will be empty. One way to retrieve an entity together with related entities is to use prefetch paths (see the manual for detailed instruction and code). Once your done with editing the inner entities, simply save the main one and that will make the updates recursively.
Now you may also keep with your sole user and deal with its company afterwards (for ressource consideration for instance).
So if you want to get the company(s) related to your user in a second fetch, you may use a filter to do so.
Your user class should contain methods such as GetRelationInfoCompanyCollectionViaUserCompany which gives you the filter you need to fetch the right company.
So you can fetch, update and save your company that way.
Now there is another way to the update without performing prio fetching (adpater scenario).
With the same filter mentioned above, you may use the UpdateEntitiesDirectly method from your adapter on a new company with the fields updated as you wish and the user filter.
Cheers
