Cast your vote for the official 2025 Inspire Pin! Designs were submitted by fellow Community members and reflect the creativity and passion of Alteryx users across the globe. Vote now!

Alteryx Server Discussions

Find answers, ask questions, and share expertise about Alteryx Server.
SOLVED

Reading HTML on Gallery

Landry
6 - Meteoroid

I have been attempting to read HTML files on Gallery without success.

 

In my research, I've seen HTML is most commonly read-in either as XML or CSV. I've attempted both ways of reading in, with both producing the results I want when doing a normal Run on Designer. It also works as desired when run as an Analytic App .

 

 

Edit: I originally thought a workflow runs at the point when Debug Mode is first open but this is incorrect. The workflow works correctly when run in Debug.

 

However, when I run Open Debug mode it fails on first instance. If I run it again in debug, it works fine. Before re-running it, the Input Data tool previewer correctly shows the data I would like but it doesn't seem to pass in on, which I'm assuming is the issue Gallery is having too.

 

Any help would be appreciated.  

3 REPLIES 3
OllieClarke
15 - Aurora
15 - Aurora

Hi @Landry could you share some screenshots please? Of the app, the data, it working locally and also the error message on Gallery

 

Thanks!

Landry
6 - Meteoroid

Hi Ollie,

 

Using the CSV method as example.

 

Here is the Action Tool config:

Action Tool.PNG

 

The Input Tool Config:

Input Data.PNG

 

The expected (working) results per the immediate parse tool after input:

Working locally - parse output.PNG

 

Here is what I meant by the first run of Debug showing the correct preview in the tool's window but not actually out-putting the data:

Failing on Debug - no data returned.PNG

 

The gallery error occurs at tools downstream: as no data is passed in, the field names are subsequently missing:

Gallery Error.PNG

  

 

   

Landry
6 - Meteoroid

For anyone who comes across the same problem: what ended up working as a solution was having lots of control containers for the multiple XML Parse tools. Not sure why that solved the issue but it did.