Create File (Flow adding slashes to my file name file path)

[Anonymous]

I am working on a flow that saves 11 excel email attachments to a shared drive folder. I am getting irradicate results when I get to the 'create file' action of the flow. Sometimes the flow creates all the files I anticipate (11) and other times I'll be lucky to get half. No matter what the outcome, succesful (11 files) or failed (less than 11), I'm getting a fail/error at the create file action. It's a 400 error and from what it's showing, FLOW is duplicating the slashes of the file name file path and returning a false 'fail'.
 
Q: Does anyone know what causes the irradicate duplicative slashes in the file name file path?
 
Error Example
File name: c27a7a37-bc08-4ea0-ae94-69d563249325_Copy of MTDBOLsReceived.xlsx
 
The requested action could not be completed. Check your request parameters to make sure the path \\\\genericcompany.net\\BRZ_Shared\\GFS\\dfs\\Transportation\\P\\S drive\\BM\\AMC\\Current Month\\Attachments/c27a7a37-bc08-4ea0-ae94-69d563249325_Copy of MTDBOLsReceived.xlsx' exists on your file system.
 
But this is my file system file path:
\\genericcompany.net\BRZ_Shared\GFS\dfs\Transportation\P\S drive\BM\MC\Current Month\Attachments/c27a7a37-bc08-4ea0-ae94-69d563249325_Copy of MTDBOLsReceived.xlsx' exists on your file system.

[rdonovan]

Did you ever find a resolution to this double slash issue? I am hitting the same thing.

[LeeHarris]

Hi @rdonovan 

If your file path is similar to the original one posted by @Anonymous the only thing that stands out to me is the mix of backslashes and forward slashes. Notice how the forward slash remained as single whilst all the others were doubled. It could be that the system is treating the backslash characters as part of the string and escaping them by replacing them with a double backslash.

I am not able to confirm if this suspicion is correct but if this solves the problem for you please let me know.

[rdonovan]

Thanks Lee, yeah that could be the case. 

What's killing me is that the connection is good, and the path is selected through the UI. Pretty straight forward.

The requested action could not be completed. Check your request parameters to make sure the path 'C:\Apps\Microsoft Dynamics\SL\Applications\Imports\Download\XML' exists on your file system.
clientRequestId: 610c6616-4b53-4bb5-a226-da1889ce7eaf

{

  "status": 400,

  "message": "The requested action could not be completed. Check your request parameters to make sure the path 'C:\\Apps\\Microsoft Dynamics\\SL\\Applications\\Imports\\Download\\XML' exists on your file system.\r\nclientRequestId: c267858a-1c6f-4e37-a50b-7e5322b38187",

  "error": {

    "message": "The requested action could not be completed. Check your request parameters to make sure the path 'C:\\Apps\\Microsoft Dynamics\\SL\\Applications\\Imports\\Download\\XML' exists on your file system."

  },

  "source": "filesystem-eus2.azconn-eus2-01.p.azurewebsites.net"

}

[Anonymous]

@rdonovan my connection was good as well. I ended up abandoning the project I was working on and chose a different product to automate with.

[obadiahjohnson]

I also have this issue. I even tried creating a string variable consisting solely of a \ but the system keeps adding them. Does anyone have any ideas on how to correct this? Maybe \ need a special character in front of them?

[obadiahjohnson]

For my issue, I found that my "connection" to the gateway wasn't set up correctly. I selected the ellipsis and selected "+Add new connection" and entered my name for the connection, default path, THIS TIME I correctly added my domain\username instead of just my username, my password, and then selected the gateway I created.  

Once I did that, Power Automate no longer tried to "escape" the backslash character by adding a \\. 

Please mark as solved if you would please. It certainly worked for me 🙂

[ashishksi]

This error primarily occurs if the absolute path(Root Folder path provided in connection + path getting generated during file transfer) of the file to be transferred is more than 256 characters. If you limit the file path size this issue won't occur.

Please mark as solved if you would please. It certainly worked for me!

[ps1982]

Not sure if it helps, but after much playing around and starting over again it turned out that I just needed to use domain/username when setting up the data gateway connection rather than username or email.