PowerAutomate - Get File Content using On-Premises Gateway - 404 Error on UTF-8 encoded filenames.

[Anonymous]

I am using the File System -  'Get File Content' actions (both variants - by id and path) and getting '

'There is no file with name .... Verify the file exists or create it before trying to access it'

The files that it is accessing have characters encoded in UTF-8 in their filenames. It is working on most files but failing on a few.

Example: ABC_A350_TEST%3FS20%%5CCHAR%2F4%5F1_50454542_0000000000_20220927.pdf

If I remove the 'TEST%3FS20%%5CCHAR%2F4%5F1' part, it works. It has worked for most other encodings, so I am not able to figure out why it is failing on just a few like this one. 

Any guidance is appreciated.

[lbendlin]

That's a hilarious error. And you say you are getting this even when accessing the file by ID ?

[Anonymous]

Yes, I am getting the same error while accessing using ID as well.  The List Files in Folder action is able to list the files, but when it comes to the Get File Content it is unable to locate the file. I really wonder how to fix this.

[lbendlin]

Let me do some tests on my side but I think this may require a pro ticket.

[lbendlin]

I tried with an Excel file with a german umlaut and a cyrillic O.  Seems to work just fine?

The raw input says that it uses the file ID rather than the name.

[Anonymous]

Thanks for testing. The file name you have used is in decoded form. Mine is encoded. Here is another example of one that is failing:

ABC_A510_TCH%5FATB%5FURRW4026ELE%5F20210811_50132190_0000000000_80344142_95123594_20220927.pdf

I am not sure if would work or fail with the Excel connector you have used, my issue is with the File System -> Get File Content (both by ID an path).

I have sent a ticket to MS, if they provide a solution, I will post it here.

[Anonymous]

The PowerAutomate product team responded that they have no solution to this time, and that they have raised this as bug. They had me send them 'additional logs' from the On-Premises Gateway and returned with this information.

They have advised me to not use filenames with encoded text (they are perfectly valid filenames in the Windows OS and SharePoint).

So, no solution to this time and I need to find an alternate way to handle special characters.

[lbendlin]

Thank you for raising the ticket. 

As I mentioned you can consider using the file ID instead of the name.

[Anonymous]

I am not sure what you mean by file ID. The Get File Content (both by ID an path) is failing when a filename with encoded text is passed as the parameter to identify the file in the file system. MS had multiple troubleshooting sessions with me and has identified this as a bug on their side and that they will come up with a fix.