When the users enters a name which is in the Excelfile s/he gets flag telling her/him that this user might be a duplicate. However, this solution is not so good for two main reasons: Two flows exist for this purpose: 1x a Power Automate Desktop flow that fetches the data from the Excel file and 1x a cloudflow that checks if there is a duplicate when creating a contact. In our use case, to keep the example simple, we have an Excel file that stores contact information. Next to it we have a second VM on which nothing else is currently happening: In the following scenario we have a VM with Power Automate Desktop and a corresponding flow. Keep in mind the following scenario is very much simplified to keep this article within reading span of most people. A clearly better solution is to scrap the old software and replace it with a modern solution, for example based on the Power Platform.
However, it should by no means be seen as a long-term solution. It does this very well, without question.
Power Automate Desktop (PAD), at least in the context of Power Automate cloud flows, is a bridging technology for applications without API. One thing in advance: The solution shown here should only be used as a last "resort" if you can't or don't want to replace the corresponding solution with a newer application that has an API (e.g. So we will show how to scale a small solution to multiple machines. However, since the practical application of this topic is relatively rare we cannot cover all uses cases. Whether you should use Power Automate Desktop or not has been described by my colleague in the community Reza Dorrani in his excellent video about this topic ( ). Scale Power Automate Desktop (PAD) using multiple Machines
0 kommentar(er)
