When using my local machine, i can create a simple app that uses the tree interface tool with a custom file specified. This is great because whenever the custom file is changed (i.e. rows are added/deleted), the workflow will recognize those changes (i.e. when i run the app, it's going out and checking a fresh copy of that file before it shows the user the options); however, our private server cannot handle a custom file for the tree interface tool that points to a UNC file. I don't want to package the file with the app. I receive an error message when I run the app. Is there something else I can do to fix the error I'm receiving in the server environment? If it's not a current capability, it would be great if it could be added. Note that I also tried using an oracle connection, which again worked on my local machine, but errored out on the server. I've included my sample workflow and custom tree file. By changing the workflow dependencies to be UNC file path, you should be able to recreate the errors I'm getting (assuming that the error I'm getting is legitimate). Thanks!
Solved! Go to Solution.
@JamesHa Can you please explain how to setup service accounts in more detail?
this should be basic functionality, that tools must be able to access input files to prepare Interface without running workflow,
Any further developments on this?
The issue is that the Alteryx Server Interface is not triggered as the Run-As-User or the User kicking off the Analytic App. It is triggered by the Windows User running the AlteryxService on the Alteryx Server. To rectify this, the XML file should live in a folder accessible to "SYSTEM" or the Log-On-As User for the AlteryxService.
I believe the Tree tool is one of the most underutlizied Alteryx components - this capability would really make it better.