![]() For the Command input we will provide "C:\Program Files\Microsoft Office\root\Office16\EXCEL.EXE" %FilePath%. We will subsequently write to this session using the Write to CMD session and use the output variable that was generated in the previous step as our CMD session input. ![]() The previous step will create a command line session. Leave the Working folder blank and then click Save. Then provide appropriate values for your Office 365 URL as your Default Value and set External name to FilePath.Īdd an Open CMD Session action to your design surface. Solutionĭefine an Input Variable called FilePath. ![]() Or is it? What we can do is send the Office 365 link, like a SharePoint link, from our Cloud flow to our Desktop flow and then use the CMD action to open the URL with the local application, Like Microsoft Excel. Without an On-premises Data Gateway, it becomes difficult to process this file in Power Automate Desktop. ![]() ![]() Currently, Power Automate Desktop only supports text input types from Cloud flows to Desktop flows, so there is no direct way to send binary files through that channel.įor example, perhaps we have an Excel file that has been added to a SharePoint library and we want it to be processed inside of Power Automate Desktop. The On-premises Data Gateway is the preferred way to send files from the cloud to a local device, but for some organizations, they have restrictions around how data is sent from the cloud to the local device. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |