Hello,
We have a Radzen Studio application where there is a page tied to a SQL Server table, and there are various elements (dropdowns, textboxes, text areas, etc.). The users are reporting that they save the data to the database (and receive a successful toast message), but later come back and see that the dropdowns they changed previously are no longer populating (like it didn't save). What is odd is that they then load the page again some time later and the data is now populating. I was trying to think of the best way to troubleshoot this. Could it be a caching issue on the browser? Or should we add logging to the page load event when it pulls the record from the table? What other things could be causing such an issue?
Thanks,
Bill
Hi @bdiplacido,
I think browse caching is unlikely.
This would definitely indicate if there are any issues that happen during loading.
We did testing yesterday in development and what was happening was that user1 and user2 both load the same record - we had user1 modify the record, then user2 would navigate away from the record, and navigate back into the record, but user1 would have stale data. Logging the data as json to the console showed stale data (so I agree don't think it is browser caching). After doing some research we tried adding AsNoTracking() to the database context like:
Context.TblMyTable.AsNoTracking().AsQueryable();
It seems to fix the above scenario. We're going to try it out in production with our users today and see if it fixes the problem for them.
Thanks!
Bill