Publishing workflow to private gallery without assets

[IanJiang]

Hi All,

I am relatively new to Alteryx. Recently I have been having trouble with the assets when publishing workflow to private gallery on our company's server. I have an input and output tool that read and write to the same file. Despite being an ordinary path on the server (not a shared/network drive), it keeps being treated as an asset, regardless of whether or not I uncheck the asset in publishing options (in below image its checked, but I uncheck it):

It doesn't matter whether its relative or absolute path, its always treated as an asset and gets re-assigned to 'externals/1' directory. This is undesirable, as the workflow needs to output to another standard location in my org. Here's a snapshot of the workflow and the offending input/output tools circled in red

Interestingly, the blue circled is an output tool that isn't treated as an asset upon publishing, despite writing to a similar location (one directory up). Its confusing why this output is immune to the effects. 

Additionally, I've tried copying and pasting the input/output circled above into a simpler workflow,

and in this simpler structure, there also is no problem unchecking the asset options, and the workflow produces no output when run from gallery, as desired. Is this location somehow being marked as an asset from the gallery, and if so is there a way around this?

[mbarone]

Can you get the output log from the Gallery (go to the workflow and you should see the results and can expand them to see the output log)?

[IanJiang]

Hi Aurora, 

Thanks for the prompt reply. Here's the requested log for the most recent run of the example. 

[mbarone]

Very odd. The input and output are externals.  Yet you're saying on your canvas they are not?  And you are using Full UNC paths?  If you're using mapped drives that won't work.  Even if you're using a D drive on your machine with the Canvas, if your Server doesn't have a D drive then it will go to externals.  

[Pingu]

Random guess, but maybe worth trying, as it solved issues for me back in the days.

Once confirmed that inputs and outputs are correct, did you try to select the whole workflow (ctrl + a)  copying it into a fresh canvas, and saving that workflow to your company's gallery? 

[IanJiang]

Hi mbarone, 

(apologies for mis-naming earlier!) I might have been unclear, but the paths are updating to their 'externals/1/' base, after I publish it from designer to the server. The paths are full UNC, although they do access the 😧 drive. Other paths using this 😧 prefix works however, so Im sure the server has access to the drive.

[mbarone]

Can you send a screenshot of your input/output configurations?  Something isn't adding up.

[IanJiang]

Mbarone, 

Here is one such input tool 

And here is the corresponding output tool in the same workflow (so the same file is being read and written to in the workflow)

To re-iterate, attempting to save to the private gallery automatically updates the path that you see in the output tool to 'externals/1', regardless of whether or not I have these unchecked in the 'Manage Workflow Assets' when publishing.

Ian