Hi Akash, Scott is right, the onsave will be callend as prevalidation before save. You can place your code in the onload but it doesn't mean will be called only after save. And we found the 'unsupported way' using this javascript function addOnPostSave(handler) { if (window.__Mscrm_save == undefined) { window.__Mscrm_save = Mscrm.InlineEditDataService.save; Mscrm.InlineEditDataService.save = function (saveMode, succeedCallback, errorCallback, sync, propagateCallbackHandler) { var tempsuccesscb = succeedCallback; succeedCallback = function (arg1) { if (tempsuccesscb != null) tempsuccesscb(arg1); Xrm.Page.data.setFormDirty(false); for (var i = 0; i < window.__post_save_events.length; i++) window.__post_save_events[i](); } //var temperrorcb = errorCallback; //errorCallback = function (arg1) { // debugger; // if (temperrorcb != null) temperrorcb(arg1); //} window.__Mscrm_save(saveMode, succeedCallback, errorCallback, sync, propagateCallbackHandler); } } if (window.__post_save_events == undefined) window.__post_save_events = new Array(); window.__post_save_events.push(handler); } And how to call: addOnPostSave(function() { alert('after Save!!'); }) Remember this is unsupported. Thanks
↧
