Table Widget Sort & Field Alias

[CameronLacelle]

Using a table widget as part of a larger experience builder that will hopefully eventually become our organization's new corporate GIS viewer, replacing our legacy system that is no longer supported.

Two questions/concerns related to the table widget:

1) Is there a way to change filed name aliases just for the table widget that do not involve needing to set aliases at the actual source?

2) All of the data used in this experience builder are referenced/registered data we've registered to our data store/Portal. Many datasets are SQL, some eGDB, and a few shapefiles. We have registered the source folder to the data store for any shapefiles. I've noticed for any shapefile, when trying to sort a field, no actual sorting occurs and the default sort order remains. Seems to only be an issue related to shapefiles as any SQL or eGDB layers sorting works fine. Anybody else encounter this and a workaround? Our team is in the slow process of getting away from shapefiles but there are lingering ones we are unable to migrate immediately.

[Shen_Zhang]

Hi @CameronLacelle, 

1. Currently there's no way to change the filed name alias in the table widget, even in the Experience Builder. 

2. Could you provide more details on how you use these shapefiles? As you know only feature layers are supported directly as data sources, and I couldn't see the sorting issue when importing local shapefiles. Could you help elaborate on it?

[CameronLacelle]

Hi @Shen_Zhang 

In ArcGIS Pro, we go to "Manage Registered Data Stores" and click "Add". We choose Folder and fill in the dialog box with a title, where to store the connection on our Portal, and choose the folder path. We validate the connection and click Create. This then allows us to publish Shapefiles to our Enterprise Portal as Referenced Registered Data rather than copies of the data (hosted FL).

We then bring our specific shapefile(s) that we want into Pro, do any symbology, labels, pop-ups, etc. in Pro and then share as Web Layer to our Portal ensuring we select "Reference registered data" and only select Map Image (Feature unchecked). When Analyzing we should not receive any warnings as we've registered the data store to our Server in the previous step.

Then when we use that Map Image Service in an Experience Builder, they're the only culprits that don't seem to sort when using the table widget in an app.

Hopefully that explanation can allow you to reproduce from your end.