Intersoft Community - Crosslight - How to Use Crosslight in Reloading an Entity and its Navigation Properties from Server-Side?

How to Use Crosslight in Reloading an Entity and its Navigation Properties from Server-Side?

leo.c — Thu, 03 Sep 2015 10:21:30 GMT

Hi Jimmy,

For your information, Entity Framework works best when database leaves all the logic to the Entity Framework code. In a case where your database trigger was complex and required more time, you could adopt one of below options:

1. Let Entity Framework to handle all complex trigger logic.
2. Make client side to reload the entity after save was done. (I believe that hotfix for GetSingleAsync issue will be available soon)
3. If you know the estimated time the trigger process will finish, you could wait several second before reload the data.

About disposing the DbContext and create a new one, may be you could create the new DbContext while leaving the original one then get the required data from the new context.

Best Regards,
Leo

How to Use Crosslight in Reloading an Entity and its Navigation Properties from Server-Side?

jtungol@silentpartnersoft.com — Tue, 01 Sep 2015 15:47:50 GMT

Any idea on how we might accomplish this on the server side using the Web API? Currently, we are using AfterSaveChangesDelegate to reload or load navigation properties, including the entity that is being updated. However, there are numerous forums that state that context cannot live long and are not meant to live long for that matter. There are suggestions that the original DbContext should be disposed and create another one. While that can be accomplished, we don't see how that is going to work with Crosslight's Enterprise design through the AfterSaveChangesDelegate. Disposing the original context also means that any change tracking behind the scene will stop. The solution provided by Arief in this thread does work at times in simple scenarios where a trigger is simple enough that the results of an updated row are refected in an instant. However, most of the triggers that we have require complex calculations that updating the expected results of a row or record might be delayed at some point; thus, it might make sense the the navigation properties are updated on the second time an entity is being saved from the client-side. That being said, we can't save the same data twice from the client-side in order to get the updated data for a navigation property.

Although triggers should be synchronous in nature, and calling SaveChanges in a DbContext should have triggered the changes of the affected rows. We don;t understand why the reload or load methods of the entity functions are unable to retrieve an update record for the navigation properties attached to the entity that has been saved. Any solutions or workarounds would be very much appreciated. Thanks!

How to Use Crosslight in Reloading an Entity and its Navigation Properties from Server-Side?

jtungol@silentpartnersoft.com — Mon, 31 Aug 2015 20:19:22 GMT

We've posted a similar question before (click here), but this approach is unstable. The first time an entity is being saved, the navigation properties should already contain the calculated data based on triggers. We have to send another save request from the client-side in order to get the updated values for the navigation properties. This is terrible, we can;t send multiple requests just to get the updated values. This leads us to refresh data from client-side by using GetSingleAsync() method from the repository, but we're getting errors using commposite keys (see here). Still this seems like multiple round trips from client-side to the server (after saving > refresh data).

Please advise! Thanks!