We have an Experience builder application with a map displaying point locations and a table of all points with about 10 fields visible. Our users need to download this table daily, and the first issue we ran into was that the "Export to CSV" button downloaded ALL fields from the raw data, not the displayed view. Our raw data has over 100 fields and renders the download almost unusable for our users. Additionally, the alias name of the fields is not carried over into either the table or the download.
Some investigating in the ESRI forums led to a post history where ESRI's work around to downloading only the fields in the table view was to select the records first. This requires users to Select All... a functionality that does not exist in tables per additional forum posts I have found.
So, the work around for the work around is to add a select widget, set it to select by attribute via a preset query, and have users click the Select widget to select all rows before downloading. This is also not very intuitive for our user base. The query used is 'Object ID is not blank'
Another issue was found after implementing these steps. The user selects all rows using the select widget and Exports to CSV. The first CSV they export is mostly empty with only the object ID and lat/long populated. They click "Export to CSV" a second time and then the csv is populated with data. The second CSV file does include just the table fields.
In summary, the following items are currently impacting users and I am hoping there is a solution to some, without having to publish a view? Our organization is using Enterprise 11.4
- The Export to CSV result does not reflect the visible fields in the Table widget, and instead downloads all fields.
- The exported csv file and the table widget both include the raw field names and not the alias.
- After rows are selected, users have to download a csv twice, with the first one being mostly empty and the second one populated with data.
