Skip to main content

Async Plugins vs. Power Automate Flows

Power Automate: SharePoint Copy file action fails on file names with a plus (+) sign

 

For data migration purposes I tried to copy files from one document library to another with the help of Power Automate's copy file action for SharePoint. At some point I realized that it always fails on file names that contain a plus (+) sign.

Checking the community pages I found this article that pointed me to the right direction to find a workaround:
https://powerusers.microsoft.com/t5/Building-Flows/Copying-sharepoint-files-with-a-symbol-in-them/m-p/675902#M91042

Although the "Copy file" action is already the second generation it seems like Microsoft has not managed to finally solve this bug as stated in article.

The community user BISK came up with a solution to replace the file path with some HTML or URI encoding. Basically, the solution its a double URI encoded string of the path we need.

We can solve this with using the encodeUriComponent() function in an expression twice.

Sample:
encodeUriComponent(encodeUriComponent('/Source/MyFolder/MyFiles with a + sign.pdf')) 

And the result would look like this:
%252FSource%252FMyFolder%252FMyFiles%2520with%2520a%2520%252B%2520sign.pdf

You can also verify the encoding yourself with using this page: https://www.urlencoder.org/



Comments

Popular posts from this blog

Yet Another Address Autocomplete PCF Control–powered by Bing

In this blog post I will not go into detail in how to install all the pre-requisites that are required to build and run PCF controls. My goal was to build a new PCF control and get into coding of PCF controls as fast as possible. Here are a few links to articles that will help you installing the pre-requisites (Microsoft PowerApps CLI)  https://docs.microsoft.com/en-us/powerapps/developer/component-framework/get-powerapps-cli Other good references to get into this topic: https://toddbaginski.com/blog/how-to-create-a-powerapps-pcf-control/ https://docs.microsoft.com/en-us/powerapps/developer/component-framework/create-custom-controls-using-pcf I looked through the Guido Preite’s https://pcf.gallery/ which will help you find appropriate use cases / examples for your own needs. It did not take very long to find a simple example to start with: Andrew Butenko's https://pcf.gallery/address-autocomplete/ A few moments later I had the idea to create yet another address autocomplete...

Power Automate: Avoid Apply to Each for List rows action (DataVerse)

If you do not want to use the Apply to Each loop after a Dataverse List rows action you can use the following in a Dynamic Content / Expression box to directly use a field's value in e.g. Compose action: first(outputs('List_rows')?['body/value'])?['apx_fullpath'] instead of apx_fullpath you can use whatever field name you need for the entity that's been queried before.

Async Plugins vs. Power Automate Flows

Choosing Your Automation Tool Choosing the right tool for automation and business logic in the Power Platform and Dynamics 365 is crucial for building scalable, maintainable, and performant solutions. Both asynchronous plugins and Power Automate flows can execute logic in the background, but they are designed for different scenarios and user profiles. This interactive guide provides a comparative overview to help you determine the most suitable option for your specific requirements. At-a-Glance Comparison This chart provides a visual summary of the relative strengths of each tool across key decision factors. Hover over the points for more details. Interactive Criterion Explorer Sel...