Using Microsoft flow you can automate and organize the flow of data between your Shopify and Microsoft D365 for Finance and Operation This the 1st part of 2. In this, I will show you how customers can be auto-created in D365 for Finance and Operation when it’s created in Shopify. First, log into Shopify as Admin. Navigate to: Settings -> Notifications -> Webhooks (Scroll to the end) -> Create Webhooks and select customer creation, and JSON format. We need a URL for sending customer details, which we will provide later. Now login to power apps or Microsoft automate with D365 account. Navigate to Flows -> New and select Instant from Blank. Now continue as shown in the below screenshots. Here the required URL will be generated after the flow has been saved. Click on the new step and search for Parse JSON. In Content select Body (parameter from previous steps). Now we need JSON schema for customers. You can find a sample Json return response from https://shopify.dev/docs/admin-api/rest/reference/customers/customer?api[version]=2020-04 Copy the response and select Generate from the sample in Powerapps and paste the response. The schema would be now generated. Click on ‘new step’. and search for Dynamics 365 for Fin & Ops. Click on Create record. Select the instance of the environment you want customers in and Entity name ‘CustomerV3’. Now you can place parameters from the previous step (Parse Json) in different fields such as. Mandatory fields that are required to create our customers are Customer account, Currency, Customer group, Company, Organization name. After the values are placed, click on Save at the top right corner. Now expand the first step and a URL will be there. Copy this URL to Shopify webhook and click Save webhook. Now let’s test this. Go to the customer’s section in Shopify and click Add Customer. Write the first name and last name for now and click save. Go to D365 F&O and navigate to All Customers. You should see a new customer created. In the next part, I will show how we can auto-create product in Shopify when created in D365 for Finance and Operation Thank you for reading!

Introduction: Using Power Automate we can format date in various formats, however we had a requirement to populate date in document in  June 10,2020  format. Solution: Here is how to achieve the same. In this example I am formatting the System date which is obtained from function utcnow(). formatDateTime(utcNow(),’MMMM dd, yyyy’) Output: If you do not need to display the full Month in words, you can write “MMM” instead of “MMMM” and get the below output.

Introduction: When your CRM and DocuSign are not connected, yet you wish to automate Closing Quote and saving your file in SharePoint, you can do it. Here is how: Your DocuSign is not connected to CRM so your first aim would be to obtain the Quote ID. This can be achieved if you populate the Quote ID on the document, before sending the document for signature. To know how to populate Word Templates using Power Automate-Check my blog: https://www.cloudfronts.in/create-and-populate-word-template-using-power-automate/ Now that you have managed to hide your Quote ID on the document, follow the below steps to complete the Use Case. Pre requisite: DocuSign Business Pro Account. [You need to check for plans as per your requirements, to use Power Automate DocuSign connector you need DocuSign Connect enabled in your account] Step 1: Use DocuSign Power Automate Connector- when an envelope status changes, set envelope event to Completed. This will trigger your flow when the DocuSign envelope is signed by all parties. Step 2: Use Action Get envelope documents. We will use this to get  the signed PDF file Content. Step 3:  Create file in SharePoint with file content from step 2. We need to read the Quote ID from the File Content , the content type is Application.pdf and not Json so you need to create a file in SharePoint first. Step 4: Use Encodian Connectors to Split and Extract the Quote ID from the PDF File. Since we have Quote ID saved on the First page of our document, we will split the pages and then pass it to Extract Text from Region Action. The Extract Text from Region will read the Quote ID saved in the given co-ordinates. Step 5: Parse the extracted data to get the Quote ID Once we have the Quote ID, we can use CDS action to update Quote Status and also move the pdf file to the correct SharePoint location using the move action in Power Automate. If you need to Close Opportunity, you may get the Opportunity ID from Quote using CDS Action and perform the action. Also if you wish to not move the PDF, you can create new Signed PDF at the correct location and Delete the existing one with SharePoint Actions like Create File and Delete File in Power Automate. Conclusion: With Power Automate it is possible to automate the Sales process even when you do not have the DocuSign connector enabled in CRM.

Introduction: While working on populating word template using Power Automate, I came across another requirement where I needed number to be populated in currency format and that’s when the Format Number action was useful. Steps: Add the Format Number Action Here, the number is your input. You can choose the available format or add custom format as below. Your input will be formatted and the Output will be as below Conclusion: Format number can also be used to trim a number after calculation to the desired format.

Like in Dynamics 365, you see a total number of records under a view. And you want similar in a Canvas PowerApp too. Here’s a simple tip to do so – CountRows() method It’s pretty simple. Using CountRows(source) method, you can get the count of records in the Source. In this case, it’s the CDS entity Accounts. To flourish how I display the count, I use the Concatenate() method and then use CountRows() inside it first show the text and then the actual count. Please note that this goes without filtering out any criteria and straight count of how many records the connection has. Your gallery could use more filtering to display lesser records if specified that way. Handle Delegation However, you need to handle a few things if you’re aware that your dataset is large. Using this formula will give a warning: And the general help offered is this – Refer this article to understand more: https://powerapps.microsoft.com/en-us/blog/powerapps-data-row-limit-for-non-delegable-queries/ Hope this helps!!

Introduction: We had a requirement where based on switch case condition, we had to populate different word templates. Power automate Action used was Populate a Microsoft Template. Since we did not want write the actions check SharePoint folder and create file in SharePoint with populated template content, we tired to store the content in an Object Variable. However, that corrupted the content. ( To understand how to populate Word Template using Power Automate check my blog – https://www.cloudfronts.in/create-and-populate-word-template-using-power-automate/). Solution: Add Action Compose and store the populate Microsoft Word Template content in that. Now store the Compose Output in the variable of type Object. Output: Below is sample output of how your file content does not get corrupted when you move it from Compose Action to a Variable.

Introduction: We are aware of dynamics 365 CRM’s Document template functionality. However document templates do not need XML Mapping which limit the fields that we can populate in template. SO here’s a way to use Power Automate and SharePoint and implement the Document template functionality. Steps: Create Word Template with content controls and Upload to SharePoint. Enable the Developer tab and click on Design Mode. From the available controls add the Content controls, repeating controls(For data table). Click on properties and add title, tag. Once done save the word and upload to SharePoint. In you Power Automate (You can trigger the power automate as per your requirements). Action 1: Get File Content. Site Address: your SharePoint link File Identifier: Your uploaded document template. Action2: Populate a Microsoft Word Template. Location: SharePoint Location. Document Library: Share Point Site Contents. File: Your uploaded document template. Content control: the content controls from your template will be visible here. Action 3: Create file. File Name: Should end with .docx File Content: will be the populated word template. Conclusion: Thus when your power automate runs, a Document will be created in SharePoint from the document template. It is easy to populate a Content control, to know about how to populate a repeating control- check my blog. Populate Repeating Control of Word Template using Power Automate.

Introduction: Power Automate makes it easy to populate word template, we can have table (Repeating control) that can be populated using Power Automate, For information on how to create and Populate Word Template- Refer my Blog: Create and Populate Word Template Using Power Automate Steps: Create a table and add content controls for each cell. After adding content controls, select the entire row and add repeating control. In Power Automate initialize an array Variable, Use append to array action and create the table you wish to populate in the Word Template. Note: Value for the array variable will be {“title in content control properties” : “actual value”} In Action populate the word template, you will see repeating control, Change the form to accept an array input, by clicking on the symbol highlighted in below screenshot. Now Add your array as input in populate word template action. Conclusion: You can populate any of your CRM Data to Word Template by using Power Automate.

Introduction: In one of our recent requirements, we had Switch case in Power Automate and then actions to be done based on the variable populated in the Switch case. If any of the case was not satisfied, we did not want to the actions after the Switch case to be performed. In such scenarios, Power Automate’s Terminate Action comes in handy. Steps: Add Action terminate. It gives option to select status( this  status will be shown in the run history of Flow). For status as Failed- power automate allows to add Code and Message for failure as well. We can also configure run of terminate based on status of previous action. Conclusion: Like Stop the Workflow Action for Workflows, We can have Terminate the Power Automate where we do not want any further action.

Have you faced a situation where a you need to create Guid for a record while working with Power Automate?? As we all know Guid is auto generated by CRM in most cases. So in case you wan to generate a Guid using Power Automate       Here is the Solution: Add compose in flow and Add guid() in expression. Output: In this way we can generate Guid in Ms flow Hope this helps !