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.