UR 12 form refresh not working
-
Thursday, January 31, 2013 4:52 PMAfter installing UR 12, I've noticed that a simple form refresh (F5) does not reload the page with the latest data! We have some silverlight web resources that change data behind the scenes and then reload the window, but when the page refreshes it is showing stale data. To take our code out of the equation, if I simply open a record in two browser sessions, change it in one session and F5 in the other, it still shows stale data.
All Replies
-
Thursday, January 31, 2013 6:20 PM
Hi KTurbyfill,
Are you using the new process forms in UR12? If so, make sure the record is actually saved before refreshing. You wil be able to tell by looking at the bottom right-hand corner if it says "Unsaved Changes".
- Roshan
Roshan http://www.magnetismsolutions.com
-
Thursday, January 31, 2013 8:59 PMNo, I'm on premise, using normal forms. I just tried in a vanilla org with none of our customizations. If I make a change in one browser window and save and close, with that record opened in another window, and then refresh (F5) the open window, I do not see the changes immediately.
-
Thursday, January 31, 2013 11:10 PM
I can confirm the same behaviour in a "playground" deployment here.
I won't allow the installation of new Rollups in our Development or Hosted environments until we've all had an opportunity to find the newly introduced issues. This looks like one of them.
--pogo (pat) @ pogo69.wordpress.com
-
Monday, February 04, 2013 6:48 PM
If anyone else can reproduce this, please say so on Connect:
I am not impressed with how little attention this is getting!
-
Tuesday, February 05, 2013 1:09 AM
Done.
But you may find that this is a "feature", not a bug. If it is a side-effect of a newly introduced caching method, it won't likely be changed. The use of F5 or window.location.reload() isn't officially supported, so it was never guaranteed not to break.
Have you tried using Xrm.Page.data.entity.save(...) to reload the page instead?
--pogo (pat) @ pogo69.wordpress.com
-
Tuesday, February 05, 2013 1:39 PMInteresting, I never considered that F5 could be 'unsupported' as a user browser action. I do plan on looking into forcing a save instead, it just makes my JS less generic because I'll have to set the submit mode to always for something that exists on the form in order for that to work.
-
Wednesday, February 06, 2013 3:49 AM
Refreshing the screen is not unsupported. Making assumptions about the implementation of the CRM and its response to a screen refresh is unsupported.
Put simply; if you cannot find a reference to something in the SDK, you cannot assume it will be supported or continue to be supported as a mechanism for the extension of CRM functionality.
--pogo (pat) @ pogo69.wordpress.com