Issue with export CSV action

[JasonBOCQUET]

Hi community, 

I have an issue with the export functionnality.

I have a Table Widget with Table (hosted) layer used on the widget. I choice 10 of my 50 columns to appears and when a user export this table to CSV he's only see the 10 columns that I choice.

I have a second Table Widget with a Feature Layer (hosted) layer used on the widget. I choice again 10 of my 50 columns to appears and when a user export this table to CSV he see ALL of the collumn in the csv.

I use exactly the same parameter between both widget, same export parameter, etc BUT it seems to be IMPOSSIBLE when it's sourced by a feature layer to have only the column that I've choiced before in the csv.

There is a way to solve this problem or it's impossible ?

[Brian_McLeer]

This may relate to BUG-000174735 which I reported as it was doing the same to me for the Query widget. I am not sure there is a workaround at this point, but I would create a case so Esri can officially record a BUG if it is one as they do not always log BUGs from Community.

[JasonBOCQUET]

Hi @Brian_McLeer i try another things : using only Table (hosted) as type of source to my table widget.

But here is a very strange things : my old table widget with my table source works to export what I want (depending of my field set in the table widget) and if I use ANOTHER table widget with the same setting, the same data source, etc, it doesn't work for it...

why there is a different result with a similar thing ??

[DougBrowning]

Also seeing that the CSV is getting the field alias, which we just added spaces to.  Most software we feed the CSV into cannot have spaces in the field names.  So we are stuck there.  No way to configure this.  https://community.esri.com/t5/arcgis-experience-builder-ideas/table-widget-export-to-csv-is-using-th... 

For poster you could create a view and then use that.  Total pain but if you are stuck it should work.