Query -> Table Widget Action Difficulty

[SteveCole]

I'm probably dense because I just find EB workflows too confusing but I'm having difficulty getting an action to do what I want. 

Backstory- I'm developing a very simple EB based front end to allow my users to export S123 records to CSV. The S123 has a feature class with 2 related tables (there are 2 repeat sections in the survey). The EB project only has a Query widget and then a Table widget below it. The Query widget is associated with the S123 web map that contains the feature class and the Table widget also points to the same S123 feature class & related tables.

Desired Workflow- Ideally, my users would select the desired records using the Query widget and then the Query widget would then select the same records in the Table widget using the Query Widget's Action. But it's not happening even if the Action pane infers that it *should* happen-

I've tried developing this initially without a Map widget and now with a map widget (hidden behind the table widget since it's not needed visually) and I can't get the Query widget to auto update / filter the table widget contents.

Before anyone asks, I know you can export records through the Query widget but I don't like how the actual export tool is buried in the interface, especially for the 2 related tables. At least with the Table widget, the user can just switch tabs and the export button is there.,

[JonM32]

@SteveCole 

I recently discovered the Manager Instant App and used it for Survey123 survey management. I was able to set it up with the feature layer associated with a survey, allowing others to edit results. There is a very simple, easy way for end users to export the results to a CSV built in. You may be able to use this out of the box or configure it for what you described above.

Manager—ArcGIS Instant Apps | Documentation

311 Requests - Street Conditions (Esri Example)

[SteveCole]

Thanks Jon for highlighting that Instant App as I wasn't familiar with it. I neglected to mention that I'm attempting all this inside Portal version 11.5. The Manager Instant App is available to me but, right now, I'm just getting a spinning circle when I launch the app. Clearly I'm doing something wrong so I need to read up on it. Only thing I don't like is it being map based. My S123 use isn't map dependent.

[ToddW_stl]

Can you use the Filter widget instead and avoid using query widget actions?  I'm a couple months out from the last time I configured an ArcGIS ExperienceBuilder app, but in theory:

• Filter widget data source is the map (layers/tables)
• Table widget data source is the map (same as above)

When the user sets Filter(s), I think it should automatically update/filter the tables, since they're using the same data source.

Since you don't need the map - have you tried this as an ArcGIS Dashboard using just the layer data as the dashboard source?  Seems like a couple selector filters in the header and a table widget with export enabled would suffice.  Note: I'm not sure how the related tables would be handled though...

[SteveCole]

Hi Todd,

As with most things ESRI, you tend to get most of the way there before stepping on a rake & get hit in the face. Your suggestion seems straightforward enough but it's not working either. I've designed the filter SQL query in the exact same way as what I've done with the Query widget but at runtime, there are no values to select in the pulldown.

Query widget SQL design:

Query widget runtime:

Meanwhile, filter widget SQL design:

and filter widget at runtime:

[ToddW_stl]

It looks like you're trying to set pre-determined filters - I set the Filter widget to use Custom filters in my solution to this other post - and users were able to select from a drop-down after choosing the field of interest.  I still may recommend trying ArcGIS Dashboards, as this is a simple filter, view, export workflow and ExB may be overkill.  Either way I'll try to set aside some time tomorrow to mock up some data and see if I can duplicate what you're trying to do.

[ToddW_stl · Accepted solution]

@SteveCole - I was able to create simple 3 question survey (parent record and 2 repeats), ExB app, and Dashboard app.  Taking a step back first, I'd be curious as to why users need to export records to CSV.  Is there a legitimate business value or requirement to export data to a static external non-report type file?  What are end users doing with the CSV?

Anyways...  I think an ArcGIS Dashboard is the way to go for you.  There are various options for finding your Site of interest (in my example, I used Names with a Category Selector filter at the top).  You could use any number of Category Selectors with an included Search bar function, OR a List widget with the Search bar, OR a map widget if you think users will be in the field (with a mobile view of the dashboard configured) and would want to click on a Site point nearby to trigger related table filtering.  I used a Table widget (no Search available, I don't think) since your initial post uses all tables.

I have Actions set on the Category filter to filter all the tables, and Actions set on the Names (parent records) table to filter the related record tables.  I also have Advanced Formatting enabled to add the visual row color to make the expected filtering more apparent.

I also confirmed the Export option from the tables only exports a CSV of the filtered data.

[SteveCole]

Thanks, Todd. I'm going to need some time to digest the example you've thrown together but it is much appreciated. I kind of have the filter widget "working" but, as you speculated, it only works on filtering the direct table and not the related tables.

I can answer the why I'm doing this, though..

My co-workers are responsible for doing monitoring on various wetland mitigation sites that we are responsible for to ensure those sites are meeting their performance requirements. Nearly 20 years ago, I had developed an Access database to store various bits of information and developed some routines which do the quantitative number crunching for all the observations that are recorded while walking the sampling transects.

In 2007/2008ish, things like Survey 123 weren't really available so the staff ended up having to record their observations down on paper and then enter them into the Access database in order to run the number crunching (there was a Windows Mobile app called hanDBase but I never got far trying to work up something with it).  We still have this work to be done and budgets are tight once again so I saw an opening to try and leverage Survey 123 to at least provide that field application that would allow users to capture the necessary data digitally.

But capturing it digitally is only half the battle- it still needs to find its way back into this Access database. That is what leads me to this thread and developing a tool to extract the data as CSVs from Survey 123 so that I can then import them into Access to perform the data crunching. This is how I end up with a feature class (the mitigation site location) and then 2 related tables (one table with parameters of all sampling transects & a second table with the observations found along each transect).

The EB front end solution is an attempt to allow those staff the ability to be self sufficient in terms of collecting, exporting, and then importing the data in order to finish these monitoring requirements. With the exception of having to manually 10 key the data back in, it's worked well up until now. I'm just hoping to close that loop and get it entered digitally on the front end.

I still have yet to develop the VBA import routines inside Access but that's all doable.

[ToddW_stl]

Understood - Dashboards should be a smaller learning curve than ExperienceBuilder, but still requires some knowledge and practice.  I think my test with ExB aligns with your experience - too many clicks and a VERY clunky workflow.  If you want more details on that, ok.... I wouldn't recommend it, but I'm happy to share.   😀

It also looks like you might just be able to Export the related records directly from within that parent table's action buttons, without needing to open the children in their own tables.

 

 

[SteveCole]

Todd I'm marking your suggestion of not using Experience Builder as the answer to my Experience Builder question. 😂  Using a Dashboard app does appear to be better in terms of UI and ease of use so I'm onboard with it. I'm already 90% there in terms of what I want it to do but I'm getting bogged down in the Actions and filtering the second related table.

I'll make a new thread over in the Dashboards area for that.