In yesterday’s post, Tracing the Dynamics CRM Form Data save Operation, I discussed identifying data that would be sent to the database when you saved a Dynamics CRM record.

Part of the issue I was facing was related to the form not completing the save operation before I opened a new form record. Since Dynamics CRM 2013 and 2015 user interface rarely opens a new window, the user was getting a warning that there was unsaved data when the page was being switched between the Account and, in this case, the Opportunity record.

So to prevent this from happening, I had to wait for the save to complete then open the new Opportunity record.

Here is the code where I do that:

    ……
    var parameters = {
        customer_id: customerId,
        customer_name: customerName,
        customer_type: customerType,
        name: Xrm.Page.getAttribute("name").getValue()
    };

    var windowOptions = {
        openInNewWindow: true
    };

    setTimeout(function () { openNewForm(parameters); }, 2000);
}

function openNewForm(parameters) {
    var windowOptions = {
        openInNewWindow: true
    };

    Xrm.Utility.openEntityForm("opportunity", null, parameters, windowOptions);
}

The Details

We are using the JavaScript method setTimeout to wait for 2,000 milliseconds (2 seconds for those of us who are not computers).

At the end of the wait period, we will call a function called openNewForm which will use the Dynamics CRM method Xrm.Utility.openEntityForm, which opens a new Opportunity form.

You may need to adjust the wait period up or down, depending on your environment. The idea is to wait long enough for the save to complete, but not long enough to irritate the user.