Unanswered

Create File from mail attachment to File path error

(0) Share

Report

Posted on by LucaPellegrino

Hi all, I am having an issue trying to automate an email attachment directly to a file path

I have followed this guide and for one reason or another it won't recognise a local path when selecting the "Folder path"

I have tried different locations for the folder path but all roads pretty much lead back to the same message.

"The requested action could not be completed. Check your request parameters to make sure the path exists on your file system"

After being runFile System > option

I was hoping someone would be able to maybe point me in the right direction in relation to the issue and what it means?

I have also attached a full copy of the flow

Many thanks,

Luca

Categories:

Using flows

All responses (5)

Answers (0)

Sort by

v-micsh-msft Microsoft Employee on at

Like
a
(0)

Report
Copy link

Link copied!

Hi @LucaPellegrino,

Which folder path you used here?

The folder path here should be a shared Folder path in UNC format. And using the file system connector requires gateway.

Like:

\\ComputerName\ShareName

Which you could found under the Folder Sharing property for Network Path.

Check to see if changing the folder path into network path would make it work.

Regards,

Michael
LucaPellegrino 24 on at

Like
a
(0)

Report
Copy link

Link copied!

Thanks Michael for the clarification. I did setup a gateway on my local machine just as a test (i know it's not best practice to set them on local machines) to try and action this Flow

I will try and use your method below and see if it helps. For my previous tests, I didn't actually use a specific shared folder path. I just tried to use C:\Temp as an example. I assume this method will not work?
LucaPellegrino 24 on at

Like
a
(0)

Report
Copy link

Link copied!

Hi again @v-micsh-msft, I can confirm that this did not work unfortunately. I still received the same error as before, even with a Shared UNC path. I ensured the gateway was connected and ready to be used and used a shared path from my local machine .. ie \\xxxx-xxx-xxx\foldername

It keeps on making reference to the request parameters and the path. I did notice in the body of the error of the flow, the path looks odd. It's added another \\ in the path, not sure if that's a bug or the proper way of resolving the URL. I'll attach a copy of the error
LucaPellegrino 24 on at

Like
a
(0)

Report
Copy link

Link copied!

Hi all, still stuck on this and need to resolve it. Is there anyone who can assist please? Any other ideas of what to do? Where it may be failing, what those errors actually are?

Thanks
tebrown Microsoft Employee on at

Like
a
(0)

Report
Copy link

Link copied!

Any resolution to this?