How to Execute an Entity Bound Action using the Dynamics 365 Web API

Adam Murchison, 05 February 2020

Executing actions from the Dynamics 365 Web API is a neat feature that allows you to execute server-side code/functions from the client side. When implementing this, there are a few hurdles to overcome which can arise when using actions that are bound to an entity rather than an unbound global action. An action can be run under ‘None (global)’ or under a specific entity. We’ll execute an action that is entity bound to Account in this blog.


Setting the parameters

When an action is bound to an entity and is not an unbound action, there are a few different things you have to do; you can read Microsoft’s documentation here. Firstly, set the property ‘boundParameter’ to “entity”, this tells Dynamics 365 that you’re using a bound action. An input parameter called ‘entity’ must be set. This parameter needs to be set to the bound entity, in this case Account. You can see how I set this in the code below using the 'target' object.


MAG.fireAction = function (formContext) {
    var accountId =;
    accountId = MAG.cleanIdField(accountId);

    var req = {};
    var target = { entityType: "account", id: accountId }
    req.entity = target;

    req.getMetadata = function () {
        return {
            boundParameter: "entity",
            operationType: 0,
            operationName: "mag_SampleAction",
            parameterTypes: {
                "entity": {
                    "typeName": "mscrm.account",
                    "structuralProperty": 5
    }; (response) { alert("Success!") }, function (e) { alert(e.message); });

MAG.cleanIdField = function (id) {
    id = id.replace("{", "");
    id = id.replace("}", "");
    return id;


Cleaning the ID

You may notice when getting the variable ‘accountId’ there’s a function call on the following line that cleans the ID by removing the curly braces. When retrieving an ID of a record from the form context it comes back in the format as shown here: "{3E3F7F97-C510-EA11-A813-000D3A79770C}". The Dynamics 365 Web API allows curly braces when passing the ID to the action but when firing logic such as a plugin or a Power Automate Flow off this action, you’ll need to use the function ‘MAG.cleanIdField’ prior to passing it through. This is only needed when you get a ‘Bad Request - Error in query syntax’ error.

In summary, there are some slight differences between entity bound actions and global actions. I hope that this blog facilitates your development when working with them and the Dynamics 365 Web API.