{"id":27627,"date":"2021-04-22T12:42:23","date_gmt":"2021-04-22T12:42:23","guid":{"rendered":"https:\/\/www.inogic.com\/blog\/?p=27627"},"modified":"2021-09-02T06:39:01","modified_gmt":"2021-09-02T06:39:01","slug":"details-about-new-async-onsave-events-postsave-async-onsave-event-in-dynamics-365-crm-dataverse-powerapps","status":"publish","type":"post","link":"https:\/\/www.inogic.com\/blog\/2021\/04\/details-about-new-async-onsave-events-postsave-async-onsave-event-in-dynamics-365-crm-dataverse-powerapps\/","title":{"rendered":"Know Details about new OnPostSave Event in Dynamics 365 CRM \/ Dataverse (PowerApps)"},"content":{"rendered":"

Introduction<\/h2>\n

I am sure you may have used OnSave event several times in your projects. We generally use this event and write code in it to do some validation on the record to restrict the user from saving the record (using prevent Defaults method).<\/p>\n

The nature of OnSave event is synchronous. It is not the right place to call asynchronous code because it does not wait for it and we may see unsaved changes. If we make a synchronous network request in OnSave event, it can cause a slow experience and an unresponsive page.<\/p>\n

Microsoft has introduced a new Post Save event. This event is called after save event is complete and it supports after Save actions when the save event is successful or failed.<\/p>\n

We will see how this event is useful over save event. On load of Account form, I have added two events as shown below.<\/p>\n

FormLibrary.prototype.onLoad = function (execContext, attributes) {
\n\/\/\/ <summary>
\n\/\/\/ This function will load crm web api on load of form
\n\/\/\/ <\/summary>
\nvar functionName = “onLoad”;
\ntry {<\/p>\n

var formContext = execContext.getFormContext();<\/p>\n

formContext.data.entity.addOnSave(Account_FormLibrary.SaveFunction);
\nformContext.data.entity.addOnPostSave(Account_FormLibrary.PostSaveFunction);<\/p>\n

}
\ncatch (ex) {
\nconsole.log(ex.message);
\n}};<\/p>\n

Post Save Event function\u00a0<\/strong><\/h2>\n

FormLibrary.prototype.PostSaveFunction = function (executionContext) {
\nvar formContext = executionContext.getFormContext();
\nvar RecordId = formContext.data.entity.getId();
\nvar fetchXml = “<fetch version=’1.0′ output-format=’xml – platform’ mapping=’logical’ distinct=’false’>” +
\n“<entity name=’account’>” +
\n“<attribute name=’name’ \/>” +
\n“<filter type=’and’>” +
\n“<condition attribute=’accountid’ operator=’eq’ value='” + RecordId + “‘ \/>” +
\n“<\/filter>” +
\n“<\/entity>” +
\n“<\/fetch>”;
\nqueryString = {
\nFetchXml: fetchXml,
\nFormattedValues: true
\n};
\nvar accountCollction = Account_FormLibrary._crmAPI.CustomFetch(“accounts”, queryString, null);
\n};<\/p>\n

Save Event function<\/strong><\/h2>\n

FormLibrary.prototype.SaveFunction = function (executionContext) {
\nvar formContext = executionContext.getFormContext();
\nvar RecordId = formContext.data.entity.getId();
\n};<\/p>\n

Now when you click on the OOB save button, save event will trigger, and below will be the result.<\/p>\n

\"async<\/a><\/p>\n

Here the record id is coming blank because save event is not completely done. So I am not able to find related contacts. But when I check the Post save event result, I am able to get record id because it is calling once save event is completely done.<\/p>\n

\"async<\/a><\/p>\n

Here are some client API Microsoft added which can be useful while save or post save event \u2013<\/p>\n

executionContext.getEventArgs().getEntityReference();<\/strong><\/p>\n

If save succeeds, it returns entity ID, and entity name.<\/p>\n

\"async<\/a><\/p>\n

executionContext.getEventArgs().getIsSaveSuccess();<\/strong><\/p>\n

You can use this client API to check whether save operation is successful or failed.<\/p>\n

\"async<\/a><\/p>\n

executionContext.getEventArgs().getSaveErrorInfo();<\/strong><\/p>\n

This will provide the error info on save event. If we have plugin or action on create\/update of record and if it is failing then this method shows the error information thrown from the plugin or action.<\/p>\n

\"async<\/a><\/p>\n

Conclusion<\/h2>\n

You can use this information to use the new OnPostSave Event in Dynamics 365 CRM \/ Dataverse (PowerApps).<\/p>\n

\"\"<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"

Introduction I am sure you may have used OnSave event several times in your projects. We generally use this event and write code in it to do some validation on the record to restrict the user from saving the record (using prevent Defaults method). The nature of OnSave event is synchronous. It is not the\u2026 Read More »<\/a><\/span><\/p>\n","protected":false},"author":13,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"om_disable_all_campaigns":false,"_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0,"footnotes":""},"categories":[2354,44],"tags":[2171,1882],"class_list":["post-27627","post","type-post","status-publish","format-standard","hentry","category-dataverse","category-power-apps","tag-dataverse","tag-powerapps"],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/posts\/27627","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/users\/13"}],"replies":[{"embeddable":true,"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/comments?post=27627"}],"version-history":[{"count":0,"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/posts\/27627\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/media?parent=27627"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/categories?post=27627"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/tags?post=27627"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}