How-To: Translate Automatically with Microsoft Flow

In one of our previously published blog articles about Microsoft Flow, we compared the Dynamics 365 workflow with the Microsoft Flow and listed scenarios, for which business requirements, what kind of work flow should be used. One of our main points of criticisms of Microsoft Flow was the lack of native integration within Microsoft Dynamics 365 Customer Engagement. It looks like someone from Microsoft reads our blog articles and took the criticism seriously, because since the Dynamics 365 9.0 update, Microsoft Flow is natively integrated.

Briefly back to the topic of our previous blog article, where we explained the major differences between the Microsoft Dynamics 365 workflow and Microsoft Flow. The Dynamics 365 workflow allows to automate processes within the Dynamics 365 platform. Microsoft Flow, on the other hand, allows it to automate processes through a large number of different third-party applications and platforms. Thanks to the various connectors, there are almost no limits in terms of compatibility. Even for people without any programming knowledge, it is possible to build complex workflows easily. The Flow Editor is intuitive and easy to handle.

Our Microsoft Flow Scenario in Dynamics 365 v9.0

So, what is our scenario within Microsoft Dynamics 365 v9.0? We have created a Flow that could be used at INKUBIT in the future. Due to the fact that we are an international team, but the majority of our customers come from Germany, we created a translation scenario for an incoming support case. A client from Germany sends an e-mail to our support, which is transformed into a case in Dynamics 365 Customer Engagement and assigns it to the responsible developer. The description of the case should be automatically translated from German into English, so the English-speaking developer is able to understand it.

1. We create a case and fill in the description.

2. We click on the three points and create a new flow.

3. We create the flow and name it accordingly.

4. After the flow has been saved, we select the appropriate case again and execute the flow.

5. A window appears with which applications the flow connects.

6. If the flow has passed successfully, we will receive a confirmation.

7. The Dynamics User will receive the translation to the e-mail address.

Conclusion of the Native Microsoft Flow integration

Microsoft Flow has been available since April 2016 and has since then continuously improved and evolved. Improved management of flows, auditing, connectors and many more features were added. Since the Dynamics 365 version 9.0, the user does not have the feeling that Microsoft Flows has been added afterwards, as an additional feature. It feels like it has been always a part of the environment, giving the user the best possible user experience.

We are curious how Microsoft Flow will evolve and whether there might be even a merge between the Dynamics 365 workflow and Microsoft Flow one day. A consistent workflow system would, in our opinion, make absolutely sense. Who knows, maybe Microsoft will read our blog article and we are going to have a big surprise in the next major release of Microsoft Dynamics 365!