Select to view content in your preferred language

Inconsistent behavior on exporting 'selected' features from Table View widget

326
3
Jump to solution
08-21-2024 02:37 AM
Labels (1)
LakshmiKanthanM
Emerging Contributor

We have an application built using the ArcGIS Experience Builder, which is serving data from a Web Map hosted on ArcGIS Online (with an underlying feature layer). This is how the data flows in our setup:

Hosted Feature Layer (which has the data) > Hosted Feature Layer View (where filters are applied to columns) > Web Map > Experience Builder Application

We have configured a Table View widget in the experience builder application, exposing some of the data columns. Here is the issue (along with the observed behavior):

  • When we export all the data in the table (Actions > All data > Export) into CSV or JSON or Excel or GeoJSON, all fields in the Table View are found in the exported file.
  • When we select a few features in the Table View and export them into any of the aforementioned formats, data in some fields are missing. This behavior is inconsistent, at best, as we have observed data in all the fields in the exported file just once.

I am attaching the screenshots of what was done to get the exports:

capture-export-communities.PNG

This plate shows the Table View of the application built using Experience Builder (with 3 selected features, and Export to CSV) - data obscured for confidentiality.

This is the exported CSV:

FBI Crime,Offense,Case Number,Offense #,Agency,Incident Date,Location,Application ID,x,y
******,,,,,8/7/2024 4:45 PM,,233685,-13******.479,52*****.957
******,,,,,8/7/2024 3:55 PM,,233689,-13******.078,52*****.966
******,,,,,8/7/2024 6:03 PM,,233696,-13******.257,52*****.06

I've obscured the data in the fieds due to confidentiality. You will be able to notice that there is no data in the fields: Offense,Case Number,Offense #,Agency.

We do see data in these very fields when we export the entire data in the Table View:

OBJECTID,Case #,Offense Sequence,Description,Crime,Agency,Date,Location,x,y
234496,PX******,1,Cri****** Mi******,Dest******,"Pho******",8/18/2024 10:29:00 AM,"5XX N ******",-13******.4557,52*****.9605
234281,PX******,1,Muni - Park****** Res******,Other,"Pho******",8/12/2024 3:57:16 PM,"3XX O ******",-13******.925,52*****.5715
234210,MP******,3,DUII - Drivi******,Drivi******,"Med******",8/14/2024 2:07:00 AM,"W 11TH ******",-13******.0667,52*****.5887
234095,MP******,3,Muni - Exc******,Other,"Med******, OR",8/9/2024 6:40:00 AM,"1XX S ******",-13******.774,52*****.6936
... more fields...

 

Exporting is enabled both in the Table View widget and in the underlying Web Map. We are not sure how to interpret this behavior, or where to start to fix the issue. Any insight/ suggesstion in this regard would be very helpful.

Thanks!

1 Solution

Accepted Solutions
LakshmiKanthanM
Emerging Contributor

This seemed to be an issue with the feature layer view that I was using, although we were never able to figure out why exporting data from this particular view resulted in missing data in a few columns. The advice from Esri Customer Support was to recreate the feature layer view and reproduce the error. Since we were not able to, and the recreated feature layer view was working just fine, we continued using that. I am closing this issue as of now. 

View solution in original post

0 Kudos
3 Replies
ShengdiZhang
Esri Regular Contributor

Hi @LakshmiKanthanM ,

Export all and Export selected are implemented using different methods.

This should be a bug. Could you share your data and app with me? My username is she10946. Or you can contact the Support team to help reproduce your issue.

Regards,

Shengdi

0 Kudos
LakshmiKanthanM
Emerging Contributor

Hi @ShengdiZhang,

Thank you for the response. I created a support ticket as you had suggested. I am sharing the link to the support case, in case you are interested in following. I will update the findings here, in case if it helps someone else with the same issue. 

Regards,

Lakshmi Kanthan M.

0 Kudos
LakshmiKanthanM
Emerging Contributor

This seemed to be an issue with the feature layer view that I was using, although we were never able to figure out why exporting data from this particular view resulted in missing data in a few columns. The advice from Esri Customer Support was to recreate the feature layer view and reproduce the error. Since we were not able to, and the recreated feature layer view was working just fine, we continued using that. I am closing this issue as of now. 

0 Kudos