I have a workflow that is inputting file information, formatting, and saving that information across multiple Excel workbooks to a folder on my C: drive. This workflow works fine in Alteryx Designer. However, when I post it to the Gallery, the workflow doesn't run; I get an error that Alteryx couldn't read the C: drive.
Based on other comments, it seems like the Gallery does not have permission to save to a local machine. However, the workarounds I found don't work for saving multiple Excel files that are essentially dynamically named. I have tried saving to the Gallery server with no luck as well. Does anyone have insight into how to save multiple Excel files, named from a field in the file, onto a local machine from the Gallery?
I've attached screenshots, but cannot post the workflow due to client information unfortunately. See Workflow 1 for the final exporting steps that are working. The File Path Formula Tool Results, Select Tool Results, and Output Tool Results are all screenshots of these relevant functioning steps. I think the issue I'm running into is in the Output Tool, where in Alteryx I can "Take File/Table Name from Field" and "Change Entire File Path" from my field, I can't seem to do that in the Gallery.
Solved! Go to Solution.
Hi @4ensiccpa ,
When you upload the file to server, the C:\ your referencing becomes the C:\ from the server itself.
What you should do is to create a shared folder where you and your Alteryx Server has write permissions and use UNC path to address it.
To get the UNC path to your shared folder, point your input/output data tool to a file in your shared folder and go to Options > Advanced Options > Workflow Dependencies and click 'All UNC' as image below shows. Then you will see how to create your paths.
Let me know if that works.
Best,
Fernando Vizcaino
Thanks Fernando. Maybe this is a question I need to ask my internal tech team, but how would I point an output tool to a file in my shared folder? Is there a standard path for this? Or would it be unique to my company?
My internal tech team was able to identify a shared folder location that worked based on this solution. Thank you!
Great @4ensiccpa !!!!