Let your Operations Flow - Part 5

After some extremely busy weeks, I finally found some time to continue my blogs related to Microsoft Dynamics 365 for Finance and Operations and Microsoft Flow. In this part, I will elaborate on the action Get a record.

Get a record action

The Get a record action can be used to read data from your Microsoft Dynamics 365 for Finance and Operations and use the information on other actions. You can e.g. find some product details like primary vendor if you browse data from an Excel file where only an item number is specified. You can also use the action to collect data and generate an Excel file as output result of your Flow.

In this blog, I will create a simple example how to retrieve product details based on a given item number and return the primary vendor ID. We will start with a Flow button for mobile devices where you would need to enter an Item number.

After the trigger, we can add the action Get a record and we have to the specify parameters InstanceEntity name, and Object id. The field will be filled like described in my previous posts. So, the Object id requires in this example the company id and the item number.

As last step in this Flow, I used a mobile notification to inform the person about the vendor id. This will return the item number which was used as input as well as the vendor id as output.

Running the Flow

As I had used the mobile button to start the Flow, the execution will look like this:

Click the button related to the new Flow. Then provide a valid Item number.

After a short moment, you will get a notification with the desired information:

Let your Operations Flow Part 5

There is more…

Actually , when you provide a non existing Item number, this Flow will not send you a notification.

Let your Operations Flow Part 5

Instead, the Get a record action will fail. So, this action is assuming the record you are trying to find will actually exists in Microsoft Dynamics 365 for Finance and Operations. In the Flow configuration, it will be possible to setup that the next action will also run when the Get a record action failed, but still, the Flow will get the status failed at the end.

Let your Operations Flow Part 5

To bypass this error, there is an alternative which I will explain in my next blog…



I do hope you liked this post and will add value for you in your daily work as a professional. If you have related questions or feedback, don’t hesitate to use the Comment feature below.


That’s all for now. Till next time!

0 replies

Leave a Reply

Want to join the discussion?
Feel free to contribute!

Leave a Reply

Your email address will not be published.

This site uses Akismet to reduce spam. Learn how your comment data is processed.