Unanswered

Copy attachment from Email to shared folder - The character '"' is not allowed in file paths

(0) Share

Report

Posted on by DavyNix

Hi All,

Have written an simple flow to copy an attachment from an inbound Email to a folder share (via on-prem gateway). When I test the flow I'm getting the error: The character '"' is not allowed in file paths, remove or replace it before retrying.
clientRequestId: 70e5c747-bbd5-405b-ad48-ad816ff34447

The path doesn't have " character within it. Checked and double checked! It does have a hyphen but that should be ok right?

If I change the path to have a final slash (\\XX1-FileServer\Office-ABC\FTP\FTP) then the flow doesn't return the error, but just times out with: Internal Server Error

What am I doing wrong?!

Thanks in advance for any help...

Categories:

Building flows

I have the same question (0)

All responses (3)

Answers (1)

Verified answer

miguelcas Microsoft Employee on at

Like (0)

Report

Hi @DavyNix

I'm going to help you with your issue. First, I saw in your screenshot that your trigger it's not including the attachments. Second, we need to use the Create File action to create a new File in your folder because the email is arriving with a new file. Please Take a look to the following flow as an example.

Let me know if this works for you.

Thank you for using Microsoft Power Platform Communities.
Community Support Team - Miguel Castro.
If this Post helps, then please consider Accept as solution to help the other members find it more quickly.

Was this reply helpful? Yes No
DavyNix 71 on at

Like (0)

Report

Hi @miguelcas , thanks for the reply. I'm getting the error below. It seems to be adding a / to the path.

and then displaying the error: The requested action could not be completed. Check your request parameters to make sure the path 'C:\OnPremGateway\SB/new 2.txt' exists on your file system.
clientRequestId: 05f76566-a403-4a6b-9081-f0ee6d3b1f71
The attachment name is correct so I feel we're getting closer!

Was this reply helpful? Yes No
DavyNix 71 on at

Like (1)

Report

@miguelcas Ignore me - this second issue was caused by me not entering the user name correctly! User name must be Domain/username and not just UserName !! Thanks for your help 🙂

Was this reply helpful? Yes No