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?
