Dropdown-enabled Analytic App fails in Gallery

We are facing an issue when publishing an Analytic App with a dropdown interface tool to our Alteryx Gallery (Server version 2024.2).

Issue Summary:

- The analytic app runs successfully in Alteryx Designer.

- When the same app is published to Alteryx Gallery and executed from the browser, it fails immediately after selecting a value in the dropdown.

- If we remove the dropdown interface tool and publish the same workflow as an app, it runs successfully in Gallery.

Requesting to kindly help us identify the cause of this issue and resolve this error.

Gallery

Accepted answers

All comments

abacon

@BharathKumaran How is the dropdown configured? It is hard to say why this is failing without seeing the dropdown configurations.

Bacon

BharathKumaran

Thanks for the reply.

The dropdown is configured as an External Source with a file input (.yxdb).
The file contains two columns — NAME and VALUE.
Also please find attached the analytic app.

app2.yxwz

abacon

@BharathKumaran I will take a look when I can but off the top of my head - does the server have access to the YXDB file used? I would look where the YXDB file is located - does the server machine have access to the file? If so, is the file path used the UNC path? Meaning the fully path, no mapped drives.

I will take a look though here soon and let you know if I have any other thoughts.

Bacon

BharathKumaran

yes, it fails and there are no entries in workflow results

abacon

@BharathKumaran I never seen that, this might be a question for alteryx support. Have you been able to run an app before on the server?

Bacon

jrlindem

I agree with @abacon this sounds like a good one for Alteryx Support.

In thinking about this, though, I'm wondering how your drop-down list is being populated. Is it from another file or from a separate path from within the workflow, or manually set? I'm also kind of curious how the interface tool and the upstream list feeding the tool is configured if that's the method. I've seen other posts on the community where the name:value syntax isn't being followed. I don't suspect that's the case here, since you said it runs locally. This is why I'm inclined to believe the information feeding that tool isn't getting there fully or there's a sequencing issue. Are you able to post any screenshots of the workflow around the interface tool and the configuration f that drop-down tool?

Last thing I can think of is I've had apps fail on Gallery due to stale credentials for the "run as" credential that the workflow/app leverages. If this happens, the prompts, questions, or inputs for the user don't show up. That said, it doesn't say it "failed" but your screenshot has some semblances of what I've experienced in other situations.

Anyway, lots of potential areas to explore. But as Bacon stated, this might be a good one to go straight to support for.

Hope you can get this resolved. If you do circle back here and post what resolved it for other's benefit! -Jay

apathetichell

Is the error before the dropdown is loaded? if so---> Most logical explanation ---> you have access to the location of the .yxdb file --- the worker node running the workflow when it's executed on Server does NOT have access to the underlying .yxdb file.

Your description is the error is AFTER the dropdown is loaded --- that would mean that the workflow cannot find the file. there's nothing there. that would point to an issue on the worker node executing the workflow having access to the network location. This is not the same thing as the server VM having access. Server VM has access if you/on the server has access to the the file. Worker would have access if the worker vm as the worker user has access. These are not the same.

if this works as dropdwon->text input -> file output. Look at the worker user/worker node and their ability to access the file.

Quick Links

This months top contributors

atcodedog05 19598

Qiu 15867

binu_acs 15708

MarqueeCrew 13708

apathetichell 13703