Entity Configuration Configure the account entity in D365 with fields to hold the cloud agreement status. Two Value OptionSet

Transcription

1 Calling a Microsoft Flow Process from a Dynamics 365 Workflow Activity This post demonstrates a method to incorporate a Microsoft Flow application into a Dynamics 365 custom workflow Activity which passes parameter data from D365 to Flow, executes flow processes involving SharePoint, Outlook, and Dynamics 365, and updates an entity in D365 from Flow. Use Case The use case for this scenario is to send an approval to a Microsoft CSP customer in Dynamics 365, provide a link to the agreement document and the ability to approve or reject the agreement, and update the agreement status and acceptance date in D365 depending on the user selection. CRM Setup Entity Configuration Configure the account entity in D365 with fields to hold the cloud agreement status. Field schema name Type nealabc_microsoftcspid String Description The Customer CSP Identifier nealabc_microsoftcspagreementaccepted Two Value OptionSet Boolean that indicates if the customer has accepted the agreement nealabc_microsoftcspagreementaccepteddate Date Date the Agreement status changed nealabc_microsoftcspagreementparty Lookup The D365 contact for the agreeing party Place the new fields on the form in Dynamics 365. Figure 1: Account Form Additions Custom Workflow Activity Create a custom workflow activity using the Dynamics 365 SDK. 1. Retrieve the account entity 2. Retrieve the agreeing party contact 3. Create a JSON Request with appropriate parameters 4. Start the Flow process with an HTTP POST request // <author>bkw</author> // <date>10/10/2018 4:05:45 PM</date> // <summary>crm Integration Utility for Microsoft Flow</summary> // <auto-generated> // This code was generated by a tool. // Runtime Version: // </auto-generated>

2 using System; using System.Activities; using System.Net; using System.Net.Http; using System.Runtime.Serialization; using System.Text; using System.Threading.Tasks; using Microsoft.Xrm.Sdk; using Microsoft.Xrm.Sdk.Workflow; using Microsoft.Xrm.Sdk.Query; namespace nabc_crm_flow_utilities.csp_processes public sealed class StartAgreementApprovalFlow : CodeActivity [Input("RecordDynamicUrl")] [RequiredArgument] public InArgument<string> RecordUrl get; set; [Input("FlowRequestUrl")] [RequiredArgument] public InArgument<string> FlowRequestUrl get; set; [Input("MethodName")] [RequiredArgument] public InArgument<string> MethodName get; set; [Input("CopyTo ")] public InArgument<string> CopyTo get; set; [Input("Owner")] [ReferenceTarget("systemuser")] public InArgument<EntityReference> Owner get; set; [Input("DebugMode")] public InArgument<bool> DebugMode get; set; [Output("ResponseJSON")] public OutArgument<string> ResponseJSON get; set; [Output("Succeeded")] public OutArgument<bool> Succeeded get; set; protected override void Execute(CodeActivityContext econtext) ITracingService tracer = econtext.getextension<itracingservice>(); IWorkflowContext context = econtext.getextension<iworkflowcontext>(); IOrganizationServiceFactory servicefactory = econtext.getextension<iorganizationservicefactory>(); IOrganizationService service = servicefactory.createorganizationservice(context.userid); IOrganizationService privservice = servicefactory.createorganizationservice(null); try var url = RecordUrl.Get<string>(econtext); var recordref = new DynamicUrlParser(url).ToEntityReference(privService); //// Check for account entity. if (recordref.logicalname.tolower() == "account") if (MethodName.Get(econtext) == "StartCSPAgreementFlow") var account = service.retrieve("account", recordref.id, new ColumnSet( "name", "nealabc_microsoftcspid", "nealabc_microsoftcspagreementaccepted", "nealabc_microsoftcspagreementaccepteddate", "nealabc_microsoftcspagreementparty")); string cspid = string.empty;

3 if (account.attributes.contains("nealabc_microsoftcspid")) cspid = account.attributes["nealabc_microsoftcspid"].tostring(); EntityReference contactref = new EntityReference(); string firstname = string.empty; string lastname = string.empty; string = string.empty; string phone = string.empty; if (account.attributes.contains("nealabc_microsoftcspagreementparty")) contactref = (EntityReference)account.Attributes["nealabc_microsoftcspagreementparty"]; var contact = service.retrieve("contact", contactref.id, new ColumnSet("firstname", "lastname", " address1", "telephone1")); if (contact.attributes.contains("firstname")) firstname = contact.attributes["firstname"].tostring(); if (contact.attributes.contains("lastname")) lastname = contact.attributes["lastname"].tostring(); if (contact.attributes.contains(" address1")) = contact.attributes[" address1"].tostring(); if (contact.attributes.contains("telephone1")) phone = contact.attributes["telephone1"].tostring(); var result = Task.Run(() => StartApprovalFlow(cspId, firstname, lastname, , phone, account.id.tostring(), account.toentityreference().name, DateTime.Now.ToString("dd-MM-yyyy"), FlowRequestUrl.Get(econtext), tracer)); if (result.status!= TaskStatus.RanToCompletion && result.status!= TaskStatus.WaitingForActivation) tracer.trace("start Approval Flow Not successful. Response: " + result.result); else ResponseJSON.Set(econtext, result.result); catch (Exception ex) tracer.trace(ex.tostring()); if (this.debugmode.get(econtext)) throw new InvalidPluginExecutionException("Debug mode is enabled. To disable it change the DebugMode property in the workflow activity to false."); public static async Task<string> StartApprovalFlow(string cspid, string firstname, string lastname, string , string phone, string accountid, string accountname, string dateapproved, string flowrequesturl, ITracingService tracer) string responsestring = string.empty; ServicePointManager.SecurityProtocol = SecurityProtocolType.Tls12;

4 HttpClientHandler handler = new HttpClientHandler(); using (var client = new HttpClient(handler)) string jsonrequest = "'entity':'customerid': '" + cspid + "','contactfirstname': '" + WebUtility.UrlEncode(firstName) + "','contactlastname': '" + WebUtility.UrlEncode(lastName) + "','contact ': '" + + "','contactphone': '" + WebUtility.UrlEncode(phone) + "','accountid': '" + accountid + "','accountname': '" + WebUtility.UrlEncode(accountName) + "','dateapproved': '" + dateapproved + "'"; HttpContent contentpost = new StringContent(jsonRequest, Encoding.UTF8, "application/json"); var response = await client.postasync(flowrequesturl, contentpost); responsestring = await response.content.readasstringasync(); return responsestring; D365 Process Create a Dynamics 365 process to run the custom workflow activity using an on-demand call or a triggered basis like a property change. The workflow simply needs to check that the conditions are satisfied for it to execute and then use the custom workflow activity to start the Flow process and pass parameters to it. Figure 2: D365 Start Approval Workflow Example Process Parameters

5 Figure 3: Start Approval Workflow Parameters Parameter RecordDynamicUrl Flow Request Url Method name CopyTo Owner DebugMode Description The account RecordURL The HTTP POST Url generated by Flow when the When a HTTP request is received action is created Optional method name if there is more than one in your custom workflow activity address to copy the approval request to Optional to be used to set the user proxy Flag for turning debug on or off to show traces in the workflow. Flow Setup The Flow setup starts with a HTTP request action that triggers the flow and accepts parameters from Dynamics 365. A request is made to SharePoint to retrieve the pdf Cloud Services Agreement document for attachment to an . This may not be required if it is sufficient to send a link to the document in SharePoint. A Flow Approval process is started. The allows you to present text, buttons for action, and collect comments from within the . You could also use the flow app to approve the agreement. If the agreement is approved, the date and accepting party are updated in Dynamics 365. If the agreement is not approved, the account and technical managers are notified by .

6 Figure 4: Flow Diagram Figure 5: When a HTTP request is received action

7 The JSON Request Body "type": "object", "properties": "entity": "type": "object", "properties": "customerid":, "contactfirstname":, "contactlastname":, "contact ":, "contactphone":, "accountid":, "accountname":, "dateapproved":, "accountmanager":, "technicalaccountmanager": You can add as many parameters here as are required. The parameters will be accessible as dynamic values in subsequent actions in the Flow. The entity object is all that needs to be passed in as the POST content.

8 Figure 6: Start an Approval Action Figure 7: Condition

9 Figure 8: Update a record Action for D365 Figure 9: Send an Action

10 notification in Outlook Figure 10: Flow Approval