Reading HTML on Gallery
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Notify Moderator
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.
Solved! Go to Solution.
- Labels:
- Gallery
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Notify Moderator
Hi @Landry could you share some screenshots please? Of the app, the data, it working locally and also the error message on Gallery
Thanks!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Notify Moderator
Hi Ollie,
Using the CSV method as example.
Here is the Action Tool config:
 
The Input Tool Config:
 
The expected (working) results per the immediate parse tool after input:
 
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:
 
The gallery error occurs at tools downstream: as no data is passed in, the field names are subsequently missing:
  
   
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Notify Moderator
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.
