topic Re: Tree interface tool cannot be displayed on alteryx sever(2023.1) in Alteryx Server Discussions

Tree interface tool cannot be displayed on alteryx sever(2023.1)

Elite — Thu, 28 Dec 2023 08:51:55 GMT

How to solve the problem where the Tree tool hierarchy cannot be displayed properly on server (2023.1), but can be displayed normally in designer?

1.on sever ,the tree display 'ERR'

2.On the designer, the tree can display normally

Re: Tree interface tool cannot be displayed on alteryx sever(2023.1)

andrew_behrenfeld — Mon, 18 Mar 2024 20:27:21 GMT

Any luck on this yet? Just ran into this same error myself.

Re: Tree interface tool cannot be displayed on alteryx sever(2023.1)

jjoerger — Sun, 24 Mar 2024 23:10:01 GMT

Running into this error as well once we upgraded to 2023.1.

Re: Tree interface tool cannot be displayed on alteryx sever(2023.1)

KGT — Mon, 25 Mar 2024 00:27:37 GMT

There was a Tree Interface display issue fixed in 2023.1.1.247. Whether that's this issue or not, I'm not sure. Link

In the above screenshot, it looks like the tree interface might be fed by standard alteryx tools. If that's not the case, then the below is not relevant to this issue.

The interface tools are rendered before any processing happens in the workflow.

This appears to work in designer as designer already knows what the metadata looks like on that connection going into the tree. Note that it will not refresh depending on dynamic choices in the workflow, but rather be configured based on the last metadata that Designer knows about at that point.
But on server the interface tools are rendered from what's stored in the XML or the metadata of the input connections. Not the metadata of further tools in the workflow.

If the tree interface tool is being fed by a downstream tool, then it working in designer is the anomaly, not that it doesn't work on gallery.

Re: Tree interface tool cannot be displayed on alteryx sever(2023.1)

jjoerger — Mon, 25 Mar 2024 01:52:21 GMT

In my case I have a chained app. The first workflow creates a yxdb that the second workflow should read and display values. On desktop it runs fine. On the gallery, a user receives the ERR screen similar to Elite above.

Re: Tree interface tool cannot be displayed on alteryx sever(2023.1)

KGT — Mon, 25 Mar 2024 02:29:27 GMT

I'm not sure on that then...

The only testing I can see is:

Does it occur in a non chained app?
Is the server version at least 2023.1.1.247? For this fix.
Does the same happen if the Tree tool is not in a container? (I say this as there was the control containers update and interface tools don't work in Control Containers AFAIK). Still an issue regardless of this answer, but may lead to a work-around.

From there, I would reach out to support or your CSM, if you have one.

Re: Tree interface tool cannot be displayed on alteryx sever(2023.1)

AlexFR — Tue, 09 Apr 2024 20:11:27 GMT

Hi,

We were facing the same issue.

After opening the log file : \\Workspace\Alteryx\Service\AlteryxServiceLog.log

We have seen that the error was <ExpandTree> then "There is no tree question named ""Tree (193)"""

2024-04-09 19:57:36.364000,DEBUG,8332,AlteryxService,ExpandTree,42571cfbaa0a40c0880922113b075e6d,661572165854e83ab2557428,,2024-04-09 19:57:36.354768,TEST-alteryx-01,12324,240,"ProcessWebRequest_ReadBody_TreeName: Command <ExpandTree> tree name <Tree (193)> DataSetSelected <> creds <T>"

2024-04-09 19:57:36.373000,ERROR,13528,AlteryxService,ExpandTree,42571cfbaa0a40c0880922113b075e6d,661572165854e83ab2557428,,2024-04-09 19:57:36.361768,TEST-alteryx-01,12324,240,"S:\Alteryx\Service\AlteryxService_WebInterface\src\WebInterface_Work.cpp: 118. There is no tree question named ""Tree (193)"""

2024-04-09 19:57:36.382000,ERROR,5880,AlteryxService,ExpandTree,42571cfbaa0a40c0880922113b075e6d,661572165854e83ab2557428,,2024-04-09 19:57:36.361768,TEST-alteryx-01,12324,240,"ProcessWebRequest_ReadBody_Error: Error <There is no tree question named ""Tree (193)"">"

What we have done is to move the tree component out of a radio bouton (see image the first one was with error and the second one is working fine) :

Kind regards,

Alex