Mapped Network Drives for Input, Output, and Macro Repository

wottel

So here is our scenario. We have a VM that our team uses to develop Alteryx workflows. The primary drive on this VM for all inputs, outputs, & our macro repository is the E: drive. (i.e. E:\datateam\macros)

We've recently added an Alteryx Server on a separate VM and based on this article https://community.alteryx.com/t5/Alteryx-Server-Knowledge-Base/Sharing-Macros-in-Alteryx-Designer-and-Server/ta-p/250140 we have mapped the Developer VM Edrive to our Server VM E Drive so that all paths on both machines will be identical. 

However, when trying to publish a workflow to our server, the macros & outputs are not recognized. 

From the Server VM:

-We are using a service account in our "Run as User" and I've logged in under this account to map the E drive.

-While logged in as the service account, I'm able to navigate to the E Drive and see the folders & macro repository.

-I've mapped the macro repository to this user in designer.

-I can open the workflow that I'm trying to publish and it runs without any errors.

So at least in Designer, there appears to be no issues with the mapped drive being recognized. What am I missing? How do I use a mapped drive so that we don't have to redesign our workflows to use full UNC mapping?

DavidP

I think the last question in the FAQ of the post you mentioned (Sharing macros in Alteryx Designer and Server) addresses your question:

Q. Can I use a mapped network drive to share my organizations macros with Alteryx Designer users and Alteryx Server?

A. As mapped network drives are mapped on a per user basis and do not appear to batch processes, using a mapped network drive will not work for sharing macros with Alteryx Server. It will, however, work if you are only sharing macros between Alteryx Designer users within your organization.

Batch processes is the key phrase here. When published apps are run (or scheduled) on server, they are executed as a batch process, which doesn't recognize the mapped drive.

I don't think you have to change all your workflows. If you create a network share (\\fileserver\shared folder\) and copy all you macros in there, then set up the relative path in Options> User Settings > Edit User Settings and click on the Macros tab on the Designer instance that resides on the Alteryx Server as well as your Alteryx Desktop Designer instances, the macros should be recognized in the workflows you've already built.

Another key pint to note from the article is in the 1st question in the FAQ (see underlined bit)

Q. When I publish a Workflow to my Alteryx Server environment, do I need to do anything else?

A. No. When you create a macro repository, Alteryx Designer sees macros contained within the directory as a “native macro” and references the macro using relative paths. When you publish the Workflow to Alteryx Server, the macro will continue to be referenced using a relative path based off the repository path defined in your Alteryx Server environment. You can verify that the macro is not being packaged with the workflow by checking the Workflow Options -> Manage Workflow Assets in the Save As dialog window.

Hope this helps.