Hi All,
I am pulling my hair with trying to get an on premisis data gateway setup for saving files from Sharepoint to a local server.
I have the connection setup correctly as I am able to navigate through the folder structure in Flow to select the folder I want to save to or get information from. However, when I run the flow it fails because it is not able to find the filepath
When I check the failed flow this it what it shows me:
hi,
There is Two scenario if you want to add path in your local machine than give path in this way
For user name if you are a user of any domain add user name with domain\Username
Secondly if your want to make gateway in network folder follow this step.
Starts with double slashes like \\rootfolder\folder\file .
If you find this helpful, Please mark it as solution.
Thanks,
Harry_G
Hi @Harry_G and thanks for the quick response.
The connection type is domain based as its a machine at the office.
This part of the process I already having working etc as im able to navigate the folder structure inside by root folder on MS Flow:
So I know theres nothing wrong with the connection as I can see the folders etc and when ive tried other methods with the connection that doesnt work it wont let me navigate
The issue is when I try to run it:
The error is:
hi @Anonymous,
Please check test.doc is already exist in that folder and not? This is occured when file is opened already because data is not write in file when file is opened. If file is not opened please try this formula Base64('content') or see below pic.
If this solve your problem , Please Accept it as a solution.
Thanks,
Harry_G
@Anonymous , what was your final solution here. This one always gets me too.
Here are some of the factors that cause issues with Create File & On-prem gateway:
I've also seen the connection "just take time" to get established. AKA: Didn't change anything, just started working after a given time.
Hope this helps others!
@Anonymous can you please share screen shots where your connection build with on-premises gateway?
regards,
Harry_G
It was the forward slash in the "Folder Path" that turned on the light. This is due to the fact I've already specified the path in the connection that you don't need to specify it again.