usually the onload event fires after save. after 2013 they modified the behaviour is there a workaround to have the same behaviour as 2011 in dynamics 365 ?
*This post is locked for comments
usually the onload event fires after save. after 2013 they modified the behaviour is there a workaround to have the same behaviour as 2011 in dynamics 365 ?
*This post is locked for comments
Hi,
Please check the following msdn article:
msdn.microsoft.com/.../dn481607.aspx
You have two options to do this:
Xrm.Page.data.refresh(save).then(successCallback, errorCallback);
or
Xrm.Page.data.save(saveOptions).then(successCallback, errorCallback)
// In this case you can call the refresh of the page in the success callback.
If this option does not work for you, you will need to add a polling loop using setTimeout that stops when the Id of the records is set.
Stay up to date on forum activity by subscribing. You can also customize your in-app and email Notification settings across all subscriptions.
André Arnaud de Cal... 291,269 Super User 2024 Season 2
Martin Dráb 230,198 Most Valuable Professional
nmaenpaa 101,156