Power automate is an umbrella of integrating your D365 business with any 3rd party data provider endpoint, without writing any additional code (well, of course, you need to write your logic for further processing of data, validation and additional mechanism for CRUD). An example: I have a set of Amazon AWS endpoints providing data to my Dynamics 365 finance and operations. Also known as, pub-sub model, this mechanism can expose business data in its own format. You can consume this data to your MS ERP using Flows, whereby it first handshakes (every API has security as its integral component), converts the data into the required format, and then commits (create, update, deletes) the necessary records.
Flows is a new add on to Dynamics world as compared to Ax2012 where automation meant something else.
Power Automate is an umbrella of different flavours of integrations:
Unfortunately the alluring Logic apps from Microsoft despite its all powerful set of templates and features. You would be charged every time your Logic app is executed. Consider now a system where it calls your logic app automation be executed very frequently. Consequently, your bill would be too high.
Flows on the other hand is flexible in pricing/billing:
Make your flow work as your personal secretory by choosing from Templates>> “Send myself reminder in 10 minutes”.
The following screen shows up.
Click on ‘Create flow’ to continue. Click on ‘Run’ to execute your flow:
The following screen will come up:
Click ‘Run Flow’ to start your flow. This results in the following lookup:
And this can be monitored from the Flow run history page.
You can also alter the settings further of your flow: go to Edit >> the following screen will open up:
I can change the ‘send notification’ like this:
Save the flow to execute.
Sending notifications on successful invoicing is a ‘must have’ for most businesses. Back in Ax 2012 days, We needed to write explicit codes for the same: accentuating mailers on various classes: SalesJournalCreate\\createJournal() methods. With D365, while you can still do the same, but why write code if you already have provision to do the same in Power-Automate:
a. Click on new flow from ‘+ Create’
b. Select Automated flow
c. The next step asks you to give a ‘Name’ and ‘select flow’ event/trigger point. I would recommend to skip this step for now.
d. Type ‘D365’ in the Trigger search. Choose ‘Dynamics 365 for Finance & Operations’:
e. Fill up the pop up with the following information:
Click ‘New Step’ → add action.
f. Select Mail from ‘Actions’ → click ‘Accept’ to accept the terms & conditions.
g. Fill in ‘To’: list of email Ids.
h. Subject: give a custom Subject for your email.
i. Email Body: give here a desired email content.
Additionally, you can also select ‘Advanced options’ → to select CCs, BCCs, Attachments, etc.
j. Click ‘Save’ to complete.
This will let your flows be sending email as and when a Purchase Order is received.
You can manage your data be exposed as ‘Data Lake’ in the form of oData entity. Manage and create your oData entity for the same.
You would be patched to Azure AI Model studio to model, manage and deploy big data algorithms for your machine learning processes.
All these are a very basic introduction to MS Flow/Power automate fundamentals. We would be taking up more on this in our subsequent blogs: Knowledge Lakes,Machine learnings, etc.