Using On-Premises Gateway, File System Connector, saving attachments, Writing Path with double "\\". 400 error

(0) Share

Report

Posted on by r96359

228

I have a File System Connector for an On-Premises Gateway.

That gateway is mounting a file server as drive letter "P:\" .

The File System Connector is mapping Root as "P:\COE OP\PO Files\"

In another solution I could use the "Create File" component and have a folder name such as "abc12" for Folder Path and the link would test as be "c:\flow\abc12" and the file would be saved.

I'm not sure why this isn't working now. I get a 400 error.

If I define the full path like:

P:\COE OP\PO Files\<expression value>

then the test result is

P:\\COE OP\\PO Files\\TW6x

If I define the path with just \TW6x\ , it writes '\\TW61\\' as the 400 error

If I define the path with just TW6x like I have done in the past, it writes 'TW6x' as the 400 error. (This method has worked in the past as the result should be: P:\COE OP\PO Files\TW6x)

Why do I have double forward slashes?

See images below:

Thanks in advance!

Categories:

Building flows

I have the same question (0)

All responses (4)

Answers (0)

Christopher S on at

Like (0)

Report

Hi @r96359

Can you please confirm if when you were creating the connection, on the user field you indicated DOMAIN\USER? This is one of the common reasons for this issue.

Best Regards
--
If this reply has answered your question or solved your issue, please mark this question as answered. Answered questions help users in the future who may have the same issue or question quickly find a resolution via search. If you liked my response, please consider giving it a thumbs up. THANKS!

Was this reply helpful? Yes No
r96359 228 on at

Like (0)

Report

My File System Connector was set up with domain/username.
I changed it to just username and I still get // for every directory path.
Sometimes I will even get a forward slash / for the <expression folder>/attachment pdf.

When stated in create file folder path as full path:
P:\COE OP\PO Files\<expression>
I get this:
P:\\COE OP\\PO Files\\TW61/202003311142xxxx.pdf
Not sure why Flow is returning forward slashes now?

When I changed the directory path to just the expression of the subfolder from root I get a forward slash for test result
"TW61/20200331114230428xxxx_1.pdf"

When I changed the directory path as a / the result looked good but still error-ed:
Folder path = /<expression>
I get this:
"The requested action could not be completed. Check your request parameters to make sure the path '/TW61/20200331114230428978365_1.pdf' exists on your file system.\r\nclientRequestId: 85f5fe6f-84a4-47fa-a9fd-8e60fe089c56""

I feel like this is a moving target.
Help is appreciated!

Was this reply helpful? Yes No
r96359 228 on at

Like (0)

Report

I still can't figure out why this doesn't work.
When I setup an on-premise gateway on my laptop, all is good.

Was this reply helpful? Yes No
r96359 228 on at

Like (0)

Report

@chsanche

Are you speaking of the "File System" Data Connector or the On-Premises Data Gateway?
On the "File System" Data Connector I believe I am using domain\user.
If the user field is indicated as domain\user, what would be the proper way of configuring user?

Thanks for the reply.

Was this reply helpful? Yes No