{"id":364,"date":"2022-12-13T01:47:01","date_gmt":"2022-12-12T23:47:01","guid":{"rendered":"https:\/\/www.kogero.hu\/?p=364"},"modified":"2022-12-31T11:53:18","modified_gmt":"2022-12-31T09:53:18","slug":"creating-custom-action","status":"publish","type":"post","link":"https:\/\/www.kogero.hu\/en\/2022\/12\/13\/creating-custom-action\/","title":{"rendered":"How to create custom action in Dataverse"},"content":{"rendered":"

In this post we will check how to create an custom action, which can be triggered by any entity and run a custom business logic.<\/p>\r\n

What is a Custom Action<\/h2>\r\n

A custom action is a process which category is action. This action can be triggered with a custom message, can be independent from entities and can be run a custom business logic written in C# like plugins.<\/p>\r\n

\r\n\r\n<\/p>\r\n

Creating Custom Action<\/h2>\r\n

\r\n\r\n<\/p>\r\n

Let’s see how to create a custom action through a simple example project. The business logic is as follows:<\/p>\r\n

    \r\n
  1. We need an input parameter which can be any text.<\/li>\r\n
  2. Our action will convert it to uppercase<\/li>\r\n
  3. And the converted text will be returned as an output parameter.<\/li>\r\n<\/ol>\r\n

    \r\n\r\n<\/p>\r\n

    Unlike the plugins, we do not code and register immediately, because the first step is to create an action typed process in Dataverse.<\/p>\r\n

    \r\n\r\n<\/p>\r\n

    Let’s see this step-by-step on the maker portal:<\/p>\r\n

      \r\n
    1. Create or select an existing solution,<\/li>\r\n
    2. then select action through “New > Automation > Process > Action”:<\/li>\r\n<\/ol>\r\n

      \r\n\r\n<\/p>\r\n

      \"Create\r\n
      Creating an Action from the solution<\/figcaption>\r\n<\/figure>\r\n

      \r\n\r\n<\/p>\r\n

      An action creation blade will be come in on the left, where we can provide:<\/p>\r\n

      \r\n\r\n<\/p>\r\n

        \r\n
      1. a name, which will be used for the custom message<\/li>\r\n\r\n\r\n\r\n
      2. select “None” under option “Add to” which means it will be unbound to any entities, so it will be globally available.<\/li>\r\n<\/ol>\r\n

        \r\n\r\n<\/p>\r\n

        \"Creating\r\n
        Creating new Action<\/figcaption>\r\n<\/figure>\r\n

        \r\n\r\n<\/p>\r\n

        Save it, and let’s see our new process:<\/p>\r\n

        \r\n\r\n<\/p>\r\n

        \"The\r\n
        The recently created action<\/figcaption>\r\n<\/figure>\r\n

        \r\n\r\n<\/p>\r\n

        Note that the name of the process is created from the “Unique name” and the publisher prefix.<\/p>\r\n