Tree tool and the server with external custom files

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!

TestTree2.yxzp

Topic of Interest

Interface Tools

Accepted answers

JamesHa

@patrick_digan Didn't see a response to this and saw more posts so thought I would offer an explanation:

This is actually a known limitation with the interface tools in server. These tools in server aren't executed by the engine and as such are not subject to impersonation by the Run As or Workflow Credential provided. This is because the Gallery uses a separate process (AlteryxService_WebInterface.exe) that spins up under the service account in order to handle these questions (interface tools) so it can pass the appropriate wizard values to the engine. The only way to work around this is to set a service account for the Alteryx Service at the windows level so that all processes associated with the service run as that service account. That service account will need access to any network resources or database that the interface tool will need access to. The Run As or Workflow credential will still override the service account to execute the engine as the selected user.

Let me know if you have any questions!

All comments

Joe_Lipski

Hi @patrick_digan - Did you get a resolution or clarification on this?

Have come across a similar issue...

patrick_digan

@Joe_Lipski I'll check my notes and report back, but I recall the issue was our Alteryx System Settings and the alteryxservice.exe were not both setup to run as the same service account. Once we aligned those 2 items and had the same account listed in the Alteryx System Settings and the alteryxservice.exe, the tree tool was able to grab the latest file from the network without error.

patrick_digan

@Joe_Lipski It's all coming back to me as I'm reading through my emails. I believe this was an issue with 10.0 that was resolved in 10.1 for us. Even though we had specified our service account for the alteryxservice.exe, it wasn't actually using that account when it tried to go and grab the tree file from an UNC path.

Joe_Lipski

Thanks @patrick_digan, we solved our issue by changing the 'Workflow Credentials' back to 'Always run worksflows with server or studio default credentials' in the admin section of server:

workflow creds.png

MichalK

Hi,

I'm experiencing an issue with 'Tree' tool in Gallery. I use a custom file for the tree structure, but on the gallery the interface does not show, I get "Error: The credentials could not be found." message. The file is located in network drive and I'm using my own credentials to run, the same happened when I embed the file in workflow.

Changing the Admin setting is not an option - is there another solution to this?

Thanks, Michal

JamesHa

Let me know if you have any questions!

subodhkachare

@JamesHa Can you please explain how to setup service accounts in more detail?

subodhkachare

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?

JKribs

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.

apathetichell

I believe the Tree tool is one of the most underutlizied Alteryx components - this capability would really make it better.

Quick Links

This months top contributors

atcodedog05 19458

Qiu 15866

binu_acs 15708

MarqueeCrew 13708

apathetichell 13703