update the status of the record using XrmSvcToolkit request

- 
function setState() {
    //Set the stage to send enquiry letter
    XrmSvcToolkit.setState({
        id: Xrm.Page.data.entity.getId(),
        entityName: "lead",
        stateCode: 0,
        statusCode: 1, //New
        async: false,
    });
    //Save and Reload form
    Xrm.Page.data.refresh(true).then(null, null);
}

Comments

Post a Comment

Popular posts from this blog

Calling Action using javascript with web api request in mscrm

-
Image
// how to Call action Using javascript function hanleWebLead() {     var actionName = new_actioncallusingjs;         //defien action input parameters     var aactionParameters = {         "topic" : $( "#topic" ).val(),         "firstName" : $( "#firstName" ).val(),         "lastName" : $( "#lastName" ).val()     };     var actionResponse = activieCustomAction(actionName, aactionParameters);     alert(actionResponse.newLeadUrl); } function activateCustomAction() {     var Id = Xrm.Page.data.entity.getId().replace( '{' , '' ).replace( '}' , '' );     var serverURL = Xrm.Page.context.getClientUrl();     // pass the id as inpurt parameter     var data = {   ...
Read more

how to get the XRM/FromContext on html page in D365.

-
Let’s image that you created a simple HTML web resource that needs to do some work and then pass it back to the form. Previously to do so you would use parent.Xrm. However, the problem is that previous parent.Xrm and Xrm.Page is deprecated. But know you have supported way to do so - welcome getContentWindow. syntax:  formContext.getControl(arg).getContentWindow().then(successCallback, errorCallback); 1. Create a java script webresource in Solution with below code. 2. Add the Event onLoad / OnChange on Entity Form and Pass Parameter. function Form_OnchangeOROnLoad(executionContext) {     var formContext = executionContext.getFormContext();     var wrControl = formContext.getControl("new_WebResourceName.htm");     if (wrControl) {         wrControl.getContentWindow().then(             function (contentWindow) {       ...
Read more

When to use a workflow instead of a plug-in

-
When to use a workflow instead of a plug-in? Most operations that can be accomplished by using workflows can also be accomplished by using plug-ins. However, you should use workflow processes instead of plug-ins when: Changes in the business logic must be performed by people who are not developers, or the changes should not be dependent on the availability of a developer to do the work. When custom workflow activities are defined as Workflow .NET assemblies, a person who is not a developer can use Microsoft Dynamics CRM to define the conditions when the custom actions are performed and the parameters that will be passed to the assembly. You need the ability to let users apply your workflow logic manually. With workflow processes, users can trigger the processing of workflow rules by clicking Run Workflow on the form or from a grid. XAML workflows aren’t supported in Microsoft Dynamics CRM Online. XAML workflows for on-premises Microsoft Dynamics CRM.
Read more