Table Widget - Reordering Export Fields

[JarenMiller]

Hello,

I am relatively new to Experience Builder. I am having export formatting issues. I am not sure this can currently be fixed or not. 

I have selected the appropriate fields I want to be displayed in my export table within my sheet in Experience Builder. I reordered them within the sheet in hopes that they would carry over this order when exporting into a csv. This is not the case. Is there a tip to keep the same order within the sheet and have it transfer the same order to the csv? Below are two snips. 

[gis_KIWI4]

Hi @JarenMiller, I do not believe this is possible via the ExB settings. 
You could try to re-publish(overwrite) the service with the columns in the correct order. 

https://support.esri.com/en-us/knowledge-base/how-to-permanently-reorder-fields-in-a-feature-class-u...

[Shen_Zhang]

Hi @JarenMiller 

Thanks for the feedback. This is a valid issue which has been already in the product plan. It will be fixed in further releases.

[LJackson29]

@Shen_Zhang I am also curious about this. It seems like the export now works and maintains the field order if you are only exporting the preselected fields in the table, but when you turn on additional fields, the fields get all jumbled when you export it and are not in any logical order - not the order in the underlying layer or the order in the table widget.

[PAGIS]

Hello @Shen_Zhang , any update on this functionality yet? 

[Adam_Bourque]

@Shen_Zhang I am also curious, looks to still not be updated.

[Shen_Zhang]

Hello everyone, sorry for the late response. This one fell into the cracks until @LJackson29's comment reminded me. Unfortunately, this issue has not been addressed due to the createReplica method used when exporting the data, but I think there may be a workaround.

For selected records, ExB uses queries to fetch the data and export it. When using queries, the field order can be properly respected. However, for exporting all data, considering the performance issues with large datasets, ExB always uses createReplica, which is a server-side API, and it's more reliable and efficient. The downside of it is that it doesn't honour the original field order. 

A possible walkaround is to disable createReplica for the data. To do that, you need to disable both Export and Sync capabilities when publishing the service. This walkaround should work for anonymous and general users, but not for data owners and organisation administrators (they have the full editing/export privileges even if those capabilities are turned off). Please note, as I mentioned above, it may raise performance issues when manipulating large datasets.

[LJackson29]

Thanks @Shen_Zhang for your response. What impacts will disabling Export and Sync have on a service? Our service is connected to a survey123 form.