{"id":24522,"date":"2020-08-28T04:23:45","date_gmt":"2020-08-28T04:23:45","guid":{"rendered":"https:\/\/www.inogic.com\/blog\/?p=24522"},"modified":"2021-12-06T15:13:55","modified_gmt":"2021-12-06T09:43:55","slug":"building-custom-connectors-for-power-apps-and-power-automate-flows-part-1","status":"publish","type":"post","link":"https:\/\/www.inogic.com\/blog\/2020\/08\/building-custom-connectors-for-power-apps-and-power-automate-flows-part-1\/","title":{"rendered":"Building Custom Connectors for Power Apps and Power Automate Flows \u2013 Part 1"},"content":{"rendered":"

Custom logic has until now and still being developed mostly as plugin or workflow assemblies. If you wanted to extend the default behavior of the platform on certain actions like create or update record, you developed either a plugin or workflow and then had to use the Plugin Registration Tool to register this on the appropriate message.<\/p>\n

The entire process speaks of pure Dev skills required. Say as a developer you registered the plugin on specific messages and sent it out as part of a solution for the biz users to import and get going from there, but if they needed it now to be registered on another message or entity \u2013 go find the Plugin Registration Tool in XRMToolbox and ask the developer for the steps to get it done.<\/p>\n

Step in Power Automate \u2013 the low code \/ no code platform for Biz Users or Citizen Developers as they are sometimes referred to as. Flows are similar to the traditional plugins and workflows that we have had as an option to extend and add custom code\/logic. Flows infact are now being recommended as the preferred option moving forward for your automation needs in Power Platform including the first party apps like Dynamics 365 CE.<\/p>\n

Custom Connectors<\/strong> are a way to wrap your biz logic in a container and present it for biz users\u2019 consumption as a simple click, drag, drop interface. If you have worked with Power Apps or Power Automate, you would be familiar with this screen<\/p>\n

\"Power<\/p>\n

These are connectors to various apps that perform specific actions within those apps and you as a consumer need not know how these have been implemented behind the scenes.<\/p>\n

Azure Functions:<\/strong><\/h2>\n

Custom Connectors are a wrapper around Web API or Azure functions. Azure functions in simple terms is your code base hosted on Azure. You can call your code through an http request and it can accept parameters passed either as a query string or the body of the request.<\/p>\n

Any Azure function of the type http request, can be consumed directly from Power Automate Flows using the http connector<\/p>\n

\"\"<\/p>\n

Using this connector would however require the user to know and understand, tech concepts like query parameters, headers, body and configuring this is prone to errors especially when handled by citizen developers.<\/p>\n

Wrapping this API\/Azure function into a Custom Connector, provides the ability to present the user with an easy to use and configure interface.<\/p>\n

Steps to building a connector<\/p>\n

    \n
  1. Build and host Azure function<\/li>\n
  2. Secure the Azure function<\/li>\n
  3. Configure the custom connector<\/li>\n
  4. Setup the security configuration for your connector<\/li>\n
  5. Consume your connector from Power Automate Flows<\/li>\n<\/ol>\n

    Build and host Azure Function<\/strong><\/h2>\n

    You can start designing Azure function right from within Visual Studio 2019<\/p>\n

    \"Power<\/a><\/p>\n

    Next choose the Azure Version and Trigger for your function<\/p>\n

    Set it to Azure Function v2 and choose the Http trigger listed at the end.<\/p>\n

    \"Power<\/a><\/p>\n

    This sets up the project scaffolding with the default function set up there for use<\/p>\n

    \"Power<\/a><\/p>\n

    Believe it or not \u2013 with just this default code, you are actually ready to go! You have a functioning Azure function once deployed to Azure.<\/p>\n

    We will add additional code here.<\/p>\n

    Say we are accepting a Tax code as a parameter and will return the Tax Rate. We will read this from CDS entities using the .NET Core SDK currently in alpha.<\/p>\n

    To begin with, we add reference to the .NET Core SDK assemblies, we will need that to connect to CDS and read the tax rate.<\/p>\n

    Details on the .NET core assemblies can be found at https:\/\/www.nuget.org\/packages\/Microsoft.Powerplatform.Cds.Client<\/a><\/u><\/p>\n

    While using the Nuget Package Manager make sure to check the pre-release checkbox as this is in alpha at the time of writing this blog<\/p>\n

    \"Power<\/a><\/p>\n

    Now lets talk about connecting to CRM environment. Unlike plugin and workflow assemblies where you had access to the execution context, Azure functions as stand-alone functions and therefore you need to explicitly establish connection with CRM to perform read\/write operations.<\/p>\n

    We will use the Service Principle Name or Application User for connecting. This requires you register an application in Azure and get the Client Id and Secret required for connection.<\/p>\n

    The following article provides a walkthrough for this<\/p>\n

    https:\/\/docs.microsoft.com\/en-us\/powerapps\/developer\/common-data-service\/walkthrough-register-app-azure-active-directory<\/a><\/u><\/p>\n

    Once you have completed the app registration, you are ready to proceed with the connection<\/p>\n

    We will use the ClientSecret authentication type explained in the article below<\/p>\n

    https:\/\/docs.microsoft.com\/en-us\/dynamics365\/customerengagement\/on-premises\/developer\/xrm-tooling\/use-connection-strings-xrm-tooling-connect<\/a><\/u><\/p>\n

    \/\/set the connection string<\/p>\n

    connectionString = @” AuthType = ClientSecret; url = ”<\/p>\n

    + url + “; ” + \/\/https:\/\/xxx.crm8.dynamics.com;<\/p>\n

    ” ClientId = ” + clientId + “; ”<\/p>\n

    ” ClientSecret = ” + clientSecret;<\/p>\n

    \/\/establish connection with CDS<\/p>\n

    CdsServiceClient client = new CdsServiceClient(connectionString);<\/p>\n

    The .NET Core assemblies follow the same syntax and functions as the sdk assemblies except the change in the namespace this ensure no additional learning curve to make use of these assemblies.<\/p>\n

    Now go ahead read the tax and return this as a JSON object<\/p>\n

    \/\/check if result found<\/p>\n

    if (coll != null && coll.Entities.Count > 0)<\/p>\n

    {<\/p>\n

    rate = (double) coll.Entities[0][“msdyn_taxrate”];<\/p>\n

    dynamic resultobj = new {<\/p>\n

    rate = (double)coll.Entities[0][“msdyn_taxrate”],<\/p>\n

    isproducttaxable = (bool)coll.Entities[0][“msdyn_productstaxable”],<\/p>\n

    aadid = resp.UserId.ToString()<\/p>\n

    };<\/p>\n

    result = JsonConvert.SerializeObject(resultobj);<\/p>\n

    }<\/p>\n

    Publish this function to Azure, you could do this from right within Visual Studio. Choose Publish and provide all the connection details to the azure environment.<\/p>\n

    Once published, you should see a function app and the function listed in there, similar to the screenshot below<\/p>\n

    \"Power<\/a><\/p>\n

    This function once published is now ready to be called. But before that, lets ensure that not just about anybody can call function. This can be done at the simplest level by enabling function keys<\/p>\n

    Function keys could be created that would need to be passed with every call to the function to authenticate itself. If the key is missing or does not match the keys defined in Function keys, the request is not executed.<\/p>\n

    \"Power<\/a><\/p>\n

    To get the url to the request for testing, use the Get Function URL button<\/p>\n

    \"Power<\/a><\/p>\n

    Copy and paste this URL in Postman to test the function.<\/p>\n

    \"Power<\/a><\/p>\n

    Now for our connector, we would like to provide the ability for the user to login to their AAD account, similar to the experience that we have when using the CDS connector.<\/p>\n

    Secure the Azure Function<\/strong><\/h2>\n

    For this let us start with setting up the authentication for the Azure function.<\/p>\n

    Navigate to the Authentication \/ Authorization found under settings in the function app and enable App Service authentication and set it to Login with Azure AAD<\/p>\n

    \"Power<\/a><\/p>\n

    Choose Azure Active Directory from the list of Authentication Providers.<\/p>\n

    You are navigated to the next screen where we need to choose an App Registration<\/p>\n

    \"Power<\/a><\/p>\n

    Register a new APP for Azure function AAD authentication. Steps are similar to the app registration done before for CRM connection. Except you do not have to create a user in CRM and we do not need to provide API permissions to CRM.<\/p>\n

    In the Authentication option while creating the APP registration choose Multi-tenant option. as shown below<\/p>\n

    \"Power<\/a><\/p>\n

    The API permissions screen should appear similar to the following<\/p>\n

    \"Power<\/a><\/p>\n

    Choose this APP in the Azure Active Directory Authentication screen above.<\/p>\n

    Since we need to make sure our Azure function available from different tenants, make this change<\/em><\/strong><\/p>\n

    Navigate back to Azure function \u00e0 Authentication \/ Authorization<\/p>\n

    \"Power<\/a><\/p>\n

    Click on the Azure Active Directory and switch from Express to Advanced<\/p>\n

    This should bring up the below screen with the Client Id of your selected app already pre-set along with the issuer url.<\/p>\n

    To make this multi-tenant \u2013 CLEAR the Issuer URL and save.<\/p>\n

    \"Power<\/a><\/p>\n

    Ref: https:\/\/docs.microsoft.com\/en-us\/sharepoint\/dev\/spfx\/use-aadhttpclient-enterpriseapi-multitenant<\/a><\/p>\n

    Now if you try to execute the function through Postman you will receive an authentication error. You will need to provide authentication token to be able to execute this.<\/p>\n

    The next step is to create the wrapper around this function. We will check the steps to create a custom connector in the next part<\/a>.<\/p>\n

    One Pic = 1000 words! Analyze data 90% faster with visualization apps!<\/div><\/div><\/h2>\n

    Get optimum visualization of Dynamics 365 CRM data with –<\/em>
    \n    Kanban Board<\/a> <\/strong>\u2013 Visualize Dynamics 365 CRM data in Kanban view by categorizing entity records in lanes and rows as per their status, priority, etc.<\/em>
    \n    Map My Relationships<\/a><\/strong> \u2013 Map My Relationships \u2013 Visualize connections and relationships between Dynamics 365 CRM entities or related records in a Mind Map view.<\/em><\/p>\n","protected":false},"excerpt":{"rendered":"

    Custom logic has until now and still being developed mostly as plugin or workflow assemblies. If you wanted to extend the default behavior of the platform on certain actions like create or update record, you developed either a plugin or workflow and then had to use the Plugin Registration Tool to register this on the\u2026 Read More »<\/a><\/span><\/p>\n","protected":false},"author":13,"featured_media":24538,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"om_disable_all_campaigns":false,"_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0,"footnotes":""},"categories":[2088,18,36,44,1985],"tags":[2089,1337,1989],"class_list":["post-24522","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-custom-connector","category-dynamics-365-v9-2","category-microsoft-flow","category-power-apps","category-power-automate","tag-custom-connector","tag-power-apps","tag-power-automate-flows"],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/posts\/24522","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/users\/13"}],"replies":[{"embeddable":true,"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/comments?post=24522"}],"version-history":[{"count":0,"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/posts\/24522\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/media\/24538"}],"wp:attachment":[{"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/media?parent=24522"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/categories?post=24522"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/tags?post=24522"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}