Select to view content in your preferred language

Select Widget Export Fields

666
8
05-20-2024 09:45 AM
LRoberts_RDM
New Contributor II

We have built an Experience Builder app on ArcGIS Online. We are wanting users to be able to select taxlots and export out that data to a csv. The issue we are having is the fields that are included. Right now the only fields that are exporting are the object id, name and taxlot #. The layer has a popup configured that includes 10 fields, but I'm not able to get those to be included from the Select widget export. If I export from the Map Layers widget all the fields are included, but it does not respect the selection. 

I see a note in the Select widget settings that states that "Export is configured in the Data panel." I navigate to the data panel, choose the Taxlots layer and click on Fields, and it shows me the information below. I cannot find a way to configure this. 

Screenshot 2024-05-20 093458.png

Am I missing a configuration somewhere that will allow me to modify the fields included when I export from the Select widget?

8 Replies
GISHelp
New Contributor II

We have the same issue. Has this been resolved?

Marshal
Occasional Contributor

This seems like a bug to me.  The Select widget seems to only exports fields being used by other widgets (list of fields shown in your screenshot).  If you have a Table widget in your map, one work around is to send the selection to table and then export the CSV from the table.  This adds an extra step for end-users unfortunately.

Another possible workaround is to configure a table widget hidden somewhere inaccessible to end-users and configure the layers in the table so the correct fields are "In use", and then the Select widget exports appropriately.

Neither solution is great.  Hopefully they can get this widget fixed soon because it has been a great addition otherwise.

GISHelp
New Contributor II

Yes, we ended up discovering this intentional "feature" (Esri insists this is not a bug) when we were able to talk to Esri. We ended up adding an attribute table widget and then "marked as pending" so it was not visible to the end user, but all the fields were able to be selected for export. You are right - an extra step for app designers, and it has not been explicitly stated in any of the documentation that this "feature" exists.

0 Kudos
ericsamson_tract
New Contributor III

This is a pretty major oversight. The attribute table works for us for now, hopefully they can get this fixed.

0 Kudos
ahargreaves_FW
Regular Contributor

Yep it is....also cross posted here

0 Kudos
Ke_Xu
by Esri Contributor
Esri Contributor

Hi all,

Thanks for your feedback. As Marshal found, widget could only export fields being used by other widgets.

This is expected now. Because if one layer with lots of fields, all the fields are loading in the app, it will affect the performance of the app.

 

Thanks,

Ke

MatthewParkman
New Contributor

 I have the same gripe with the same issue. My users expect to be able to select/export records. I'm just going to say that Web App Builder did this just fine. It was DRAMATICALLY easier to work with than EB is. Maybe it has less "features" than EB but I wouldn't have noticed because my end-users aren't looking for animations and fancy charts that cause the map to zoom or filter. Meanwhile, trying to replicate what I have built in WAB through EB..... let's just say that it is incredibly frustrating. I mean, the PRINT widget just showed up this year? That's a basic function and it took this long for it to show up in the new platform? I just don't understand the development concept here.

0 Kudos
MatthewParkman
New Contributor

Though it seems that this thread has died, I'd like to ask for clarification. The work-around of adding a table and then moving it to "pending" to hide it from the user is working on my mockup/test map and the export function now exports all fields. My question is two-fold. If the reasoning for this is such that, "one layer with lots of fields, all the fields are loading in the app, it will affect the performance of the app", is this not still an issue with the layer being connected to the invisible table widget? And, by extension, am I not now adding additional burden to the app by adding a table that I do not need?

The layer that drives my map does have lots of fields and there are also a number of sub-layers, based on a query of the main layer. 

0 Kudos