DYNAMICS 365 PORTAL HOW TO CALL AND EXECUTE WORKFLOW

Calling Dynamics 365 Workflows from portals can only be done by configuring and adding buttons in entity lists or entity forms.
However, and for some requirements, you need to call a workflow from a web page that does not contain entity list nor entity form.

So, how do we do this?

All portal pages automatically include a JS reference to the file js\antiforgerytoken.js that contains an object named shell which has a method called ajaxSafePost that can be used and let you achieve request calls to the server.

How do we use this function to call workflow from the portal? Below is an example of how you could use the ajaxSafePost method to invoke the execute workflow service.

  1. I've created the below function that take the parameters needed to execute the workflow

    function ExecuteWorkflow(workflowId, entityLogicalName, recordId) {
    var urlService = "/_services/execute-workflow/41655177-b47f-ec11-8d21-000d3a4b649d"; // execute workflow URL
    var params = {};
    var workflow = {};
    workflow.LogicalName = "workflow";
    workflow.Id = workflowId; // guid of the workflow to execute
    var data = {};
    data.LogicalName = entityLogicalName; // logical name of the target entity
    data.Id = recordId; // guid of the target record
    params.workflow = workflow;
    params.entity = data;
    var jData = JSON.stringify(params);
    shell.ajaxSafePost({
    type: "POST",
    contentType: "application/json",
    url: urlService,
    data: jData
    }).done(function (r) {
    //do something
    }).fail(function (n) {
    //do something
    });
    }
  2. How do you get the execute workflow request URL?
    You can do it by adding a temporary call workflow button on an entity list or an entity form, and by using the Developer tools (F12) of your browser, you will be able to get the workflow url service from the data-url property as per the below image
    Portal execute workflow

Bonus Tips:
  • This method is tested on the Dynamics Portal Community on-premise edition
  • The workflow to be executed from the Portal should be triggered on-demand
You can check this page for more portal-related articles like :

Hope This Helps!

Comments

Post a Comment

Popular posts from this blog

DYNAMICS 365 HOW TO HIDE RECENT RECORDS FOR LOOKUP FIELD IN UCI

Image
In UCI, a lot of behaviors have been changed comparing to the Classic Web Interface such as the tabs, BPF, and many others. Today, I will be talking about one of these behaviors which is the Recent Records in lookup fields. In a brief summary, the Recent Records feature will suggest the latest records that have been searched for, where the user can select one of them, and, the list of available records of the current view will then be displayed. This is a nice-to-have feature since it might help the users to speed up data entry. However, if the lookup has been filtered to display specific records, the Recent Records will not respect this filter and will keep showing records even is they should not. This scenario can lead to selecting a record by the user that is not allowed to be selected. Therefore, in this situation, it is better to hide the Recent Records t
Read more

SEARCH BY GUID IN DYNAMICS 365

Image
Is it possible to search for a CRM record using its GUID ? Well, NO it is not possible and YES it is possible!!! As always has been, it is not possible to search for a record by its guid in Advanced Find and in the Quick view search. However, in the model-driven app Edit filters functionality, it is possible to search for a record by its Guid. How it works, let's check the 3 different places where we can search for a records. Advanced Find search Using the Advanced find feature, you cannot put a GUID value to search for. You will directly receive an error notification eventhough when you download the fetchXml, the Guid of the record will be there. Quick view search Using the search box
Read more

SAVE FORM IN DYNAMICS 365 JAVASCRIPT

Image
In Dynamics 365, you may need to save a CRM form automatically in JavaScript upon a specific action on the form. In order to do that, the function formContext.data.save(saveOptions).then(successCallback, errorCallback); can be used to save the record asynchronously with callback functions to be executed after the save operation is completed. The following example will display a successful message if the save operation is completed, and a failure message if not. formContext.data.save(1).then( function () { alert("Successfully Saved!"); }, function () { alert("Failed while saving!"); });
Read more