topic Re: Select Widget Export Fields in ArcGIS Experience Builder Questions

Select Widget Export Fields

LRoberts_RDM — Mon, 20 May 2024 16:45:58 GMT

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.

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

Re: Select Widget Export Fields

GISHelp — Mon, 01 Jul 2024 14:30:46 GMT

We have the same issue. Has this been resolved?

Re: Select Widget Export Fields

Marshal — Tue, 30 Jul 2024 17:35:19 GMT

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.

Re: Select Widget Export Fields

ericsamson_tract — Fri, 02 Aug 2024 18:50:10 GMT

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

Re: Select Widget Export Fields

GISHelp — Mon, 05 Aug 2024 18:54:58 GMT

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.

Re: Select Widget Export Fields

ahargreaves_FW — Mon, 05 Aug 2024 18:58:21 GMT

Yep it is....also cross posted here

Re: Select Widget Export Fields

Ke_Xu — Fri, 16 Aug 2024 10:08:37 GMT

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,

Re: Select Widget Export Fields

MatthewParkman — Fri, 16 Aug 2024 21:08:01 GMT

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.

Re: Select Widget Export Fields

MatthewParkman — Thu, 05 Sep 2024 13:57:59 GMT

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.

Re: Select Widget Export Fields

Ke_Xu — Wed, 14 May 2025 08:53:36 GMT

Hi All,

After the February 2025 update, the Select widget and Feature Info widgets load pop-up fields in data actions. It will export the fields used in Popup. And it will be released on the upcoming Portal 11.5.

Thanks,

Re: Select Widget Export Fields

MatthewParkman — Fri, 13 Feb 2026 13:30:48 GMT

That's great except that large, interconnected organizations cannot always just run up to the latest update and many of us are often stuck in a particular version for extended periods of time. It's frustrating to have to use workarounds for weaknesses in development and to be told that "the next version will be better" knowing that, for some of us, the next update could be months away.

Re: Select Widget Export Fields

Jennifer_Parmeley — Thu, 23 Apr 2026 22:01:13 GMT

In there more information about this somewhere?

Re: Select Widget Export Fields

Jennifer_Parmeley — Mon, 27 Apr 2026 17:56:04 GMT

The update is really close to being what we need, but the survey guys have requested the CSV to be exact.

Can we remove OBJECT ID from the table?
What about the extra x,y at the end? Where is that even coming from? The X,Y,Z are the coordinates our folks need.