Webfs drives not recognized for Absolute Path

[TimN]

Hi,

We move WFs and macros from test to Prod manually.  We have Test servers where we had a webfs drive mounted to worker node as a mapped letter and use absolute path to save WFs to the Gallery.  The designated drive letter is mapped to distinct websfs drives so we don't need to change the absolute path when we move from test to prod. We use this drive for any assets but not for data input or output.  so

Z:\ = Test Webfs drive on Test Worker Node for Macros

Z:\ = Prod Webfs on Prod Worker Node for Macros

This worked fine but we've added another mounted drive to be used for data we cannot publish to the Gallery with Absolute path.  Everything is switched to relative.

X:\ = Test Webfs drive on Test Worker Node for Data

X:\ = Prod Webfs on Prod Worker Node for Data

Again, the single mounted webfs worked fine and we used Absolute path all the time.  Adding the additional mounted webfs seems to be the problem.  We don't get an error - just automatically switches to relative (.\external\).

Thanks.

Server version = 2019.3

[joshuaburkhow]

The only thing I can think of at the moment is to check the "Manage workflows assets" and ensure that those inputs are "NOT" checked. 

Also you do know there are migrate APIs that you can use to move workflows 😉 https://community.alteryx.com/t5/Alteryx-Server/Migrating-Workflows/ta-p/335774

[TimN]

Joshua,

Thanks.  We do uncheck assets but defaults to relative no matter what we do.  We will check out the apis for migration.

Thanks,

Tim

[alyon]

Hi @TimN - did you ever figure this out? It just started happening to us. 

[TimN]

Hi Alyon,

We gave up on trying to add an additional drive and just use the one mapping.  I like the idea of mapping to a drive letter because it works for the way we test and deploy but it seems like Alteryx suggests UNC path is the best practice. 

Good Luck with your issue,

Tim  

[alyon]

@TimN - thanks for the quick response!