javascript - Navigation properties do not get refreshed -

I have a home unit that I send from my server to my server

  public home {public home id {set; Set;} public string address {get; Set;} public iconback & lt; Cell & gt; Room {find; Set;}}  

All data management on the client side is controlled by bridges.

My web application is Multiuser whenever a user updates a Home unit, the server notifies all interested clients using the SignalRs. When the customer is notified, it runs the following query to refresh its cache:

Refresh the function (home id) {var query = entityQuery.from ('home'). WithParameters ({homeId: homeId}); Return Manager ExecuteQuery (query) .file (queryfailed); Function queryfailed (data) {// error}}

Server side controller:

  [HTTPGATE] Public home home (int home id) {var home = _context.Context.Homes Include (T = & gt; T. Rooms). FirstOrDefault (t = & gt; t.HomeId == homeId); Return home; }  

Problem

When a home unit is refreshed, all properties will be replaced by new values ​​from the server Receive but no Navigational Properties If a user adds Cell to a given home by adding / removing, then related to the room cache is refreshing Not even though the JSN data looks OK and it includes / removed the Cell organizations.

Question

Is there an easy way to tell buffer Home and its all navigation properties? Ideally, I want to do this without cleansing the cache as explained to avoid some unsteadiness on my UI.

Update I

I tried to expand my query by room by

  Var query = entityQuery.from ('Holmes') .withParameters ({homeId: homeId}) to include Expand ("room");  

The same issue is still, JSN data changes are made by other clients but local organizations

update second

I managed to get change to promote customers using extension . However, when only rooms are added, but when they are deleted The changes are then spread.

Just to clarify, I guess you're adding a "room" to a customer Is being removed from a "house" and these updates are not being refreshed correctly on the other customer with the same "home".

If this is the case, then the reason for this is that the air client is able to determine which rooms have been added from "other rooms" to other clients, but it can not be decided Which rooms are moved or removed, rooms are also required.

To clarify, if Cell 1 has been moved from House 1 to House 2, then Client A. Clients B is currently Room 1 cell. When Client B required home 1 (Include one) it will not return any room, but will not remove cell 1 from air 1 because it does not know where it has gone. If you were making room 1 or house 2 with "room", then there would be enough information to "move" in the air room.

One way you can just follow the isolation in the "All" room connected to a specific house before "refreshing" the house. You will "lose" any house that was taken to another house but it will likely be refreshed again from the freshness of that house.

Of course this is clear, but ...