{"id":12038,"date":"2018-06-18T17:51:31","date_gmt":"2018-06-18T12:21:31","guid":{"rendered":"https:\/\/www.inogic.com\/blog\/?p=12038"},"modified":"2019-07-10T09:38:35","modified_gmt":"2019-07-10T09:38:35","slug":"integrating-dynamics-365-with-azure-functions-part-3","status":"publish","type":"post","link":"https:\/\/www.inogic.com\/blog\/2018\/06\/integrating-dynamics-365-with-azure-functions-part-3\/","title":{"rendered":"Integrating Dynamics 365 with Azure Functions – Part 3"},"content":{"rendered":"

\"Integrating<\/strong><\/p>\n

Introduction:<\/strong><\/p>\n

In\u00a0our last post<\/a> about\u00a0Azure functions, we saw how to register the workflow assembly and execute the workflow using Microsoft Flow in Dynamics 365. Continuing with our series to call webhooks from CRM, let us register the Azure function created as a Webhook. We register this using the Plugin Registration Tool (PRT)<\/p>\n

From the PRT choose Register\u00a0\u2192 Register New Webhook<\/p>\n

\"Integrating<\/p>\n

In the Endpoint URL provide the function URL.<\/p>\n

Choose Authentication method as WebhookKey and provide the key. This key is what you passed as the code querystring earlier.<\/p>\n

Note: Webhook is registered as Service End Point in CRM<\/p><\/blockquote>\n

\"Integrating<\/p>\n

You can now register a step for this webhook just like we do for a plugin assembly.<\/p>\n

\"Integrating<\/p>\n

When you create an Account the PluginExecutionContext is received in the message body of the httprequest in your Azure function. You then need to parse that to get context related details.<\/p>\n

Once registered as webhook, you can also invoke this through a workflow by executing the endpoint using the following code:<\/p>\n

string serviceEndPoint = WebhookURL.Get(executionContext);\r\n                IWorkflowContext context = executionContext.GetExtension<IWorkflowContext>();\r\n\r\n                string fetch = @\"<fetch>\r\n                  <entity name='serviceendpoint' >\r\n                    <attribute name='serviceendpointid' \/>\r\n                    <attribute name='name' \/>\r\n                    <attribute name='authtype' \/>\r\n                    <attribute name='url' \/>\r\n                    <filter type='and'>\r\n                      <condition attribute='contract' operator='eq' value='8' \/>\r\n                      <condition attribute='url' operator='eq' value='\" + serviceEndPoint + @\"' \/>\r\n                    <\/filter>\r\n                  <\/entity>\r\n                <\/fetch>\";\r\n                EntityCollection coll = crmWorkflowContext.OrganizationService.RetrieveMultiple(new FetchExpression(fetch));\r\n\r\n                if (coll != null && coll.Entities.Count > 0)\r\n                {\r\n                    IServiceEndpointNotificationService endpointService =\r\n                             executionContext.GetExtension<IServiceEndpointNotificationService>();\r\n\r\n                    crmWorkflowContext.Trace(\"serviceEndPoint found: \" + coll.Entities[0].Id.ToString());\r\n                    endpointService.Execute(coll.Entities[0].ToEntityReference(), context);\r\n                }\r\n<\/pre>\n
Once again you receive the Workflow context in the message body that you can parse to read the information passed.<\/p>\n
Conclusion:<\/strong><\/p>\n
There are other ways to invoke Azure functions from D365. Azure functions can be called through Logic Apps and you could register Logic Apps on D365 entities and actions. That\u2019s content for another post. So Keep visiting this space \ud83d\ude42<\/p>\n
\"Generate<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"
Introduction: In\u00a0our last post about\u00a0Azure functions, we saw how to register the workflow assembly and execute the workflow using Microsoft Flow in Dynamics 365. Continuing with our series to call webhooks from CRM, let us register the Azure function created as a Webhook. We register this using the Plugin Registration Tool (PRT) From the PRT\u2026 Read More »<\/a><\/span><\/p>\n","protected":false},"author":13,"featured_media":12051,"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":[5,16,18,19],"tags":[542],"class_list":["post-12038","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-azure-functions","category-dynamics-365","category-dynamics-365-v9-2","category-dynamics-crm","tag-dynamics-365-azure-functions"],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/posts\/12038","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=12038"}],"version-history":[{"count":0,"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/posts\/12038\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/media\/12051"}],"wp:attachment":[{"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/media?parent=12038"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/categories?post=12038"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/tags?post=12038"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}