Dynamics 365 Finance & Supply Chain with Power Automate - Part 2 - Adding a new customer

I recently presented a session on using Power Automate with Dynamics 365 Finance and Supply Chain.  The session was very well received, so I wanted to post some videos and details to help users better understand the examples I covered in the session.

In the following video I will walk through using Power Automate with Dynamics 365 Finance & Supply Chain to manage a workflow around adding a new customer.

Business scenario – The sales team adds new customers to Dynamics 365 Finance, but the company wants a business workflow in place, so the credit team can review the account and set the credit limit before any activity takes place on the new customer.

Components used in the scenario – Dynamics 365 Finance virtual entities, Power Automate and Microsoft Teams and/or Outlook

Synopsis – By using an Automated cloud flow in Power Automate the system can automatically manage this business process.  Power Automate will listen for new rows (customers) being added to the Customers V3 data entity.  It will update the row to make sure the customer is on hold, and it will send the information to the appropriate users in Teams and/or Outlook to review the customer and set the credit limit.


In order to follow the steps in this blog, it is necessary to have the CustomerV3 virtual entity visible in Dataverse.  If you need additional information on virtual entities, you can review my article Virtual Entities and Dynamics 365 Finance and Supply Chain Management

To get started you will begin with an automated cloud flow using the "When a row is added, modified or deleted" trigger from Dataverse.


The first step of the flow is the trigger.  Since we want the flow to only run on new accounts, the change type is "Added" and the table name is the virtual entity "Customers V3".  If you do not see the Customers V3 entity, you need to activate it in the Dataverse.


The next step is to update the new customer that was just added.  You will use the same table name as above, and the row id is the Customers V3 unique id.  (This is found in the Dynamics data)




The final step is to post a message to Teams.  This is done with the Teams connector and the settings will vary depending on how your team is configured.  In my example, there is a Credit Management team, so the message is posted to that channel.


At this point, the flow is complete, and all you need to do is add a customer to test it.

In the following video, I walk through the steps of creating the flow and show how it works.



Hopefully you find this blog and video useful.  Please feel free to comment, and be sure to subscribe to my blog and video channel to get updates on new content.

Comments

Popular posts from this blog

Creating a date table with a fiscal year in your Power BI data model

Showing the last 12 months based on a date slicer

Using Excel, OneDrive and Power Automate for Dynamics 365 Finance & Supply Chains Journals