Table Widget "Use Layer Settings"

[vic7oria]

Use what settings, under "Configure Fields"? I have set visibility, display names, and order in Field Maps and the Visualization area in AGOL and nothing changes in the table. So what is that really connected to besides defaults or alphabetical? Yes, I have checked I am connected to the right layer in the right map for the Field Maps part. 

[AnthonyJonesRSK]

Hi @Shen_Zhang,

Just wondering if this issue is likely to be addressed in the upcoming update? I've just come across this problem myself and have a table where I want to configure the same layer in multiple sheets with different filters but it is ignoring the pop up settings that are applied in both the map and to the layer via the visualisation tab. This means I will have to configure 40 plus fields multiple times.

Also, is there any possibility that the ability to duplicate sheets in a table may be added soon? This would align it with the options you have for views in a section and would be a great time saving addition.

Thanks

Anthony

[DougBrowning]

We have the same issue it keeps using alphabetical and ignores our field order which we spent a ton of time on.  Even when using Layer settings.  We found that if you flip to customize it then goes back to DB field order.  This is really the opposite of what it should do. 

Where is the world is alpha even coming from?  No Arc product has ever done that.

Then is you use the select tool and then view in table those results it yet again goes back to alphabetical sometimes.  Just so inconsistent.

Please take out alphabetical everywhere to fix this for good.  DB order is what we will always want.

Also if more than 50 fields you have to turn them on manually.

[KDHEITGIS]

Same issue! We have done all the settings in the web map and the EXB doesn't follow it when using Interact with Map widget option

[DougBrowning]

We have found this workaround

Manually in some setting in ExB buried deep - you have to flip it from honor the layer properties, to custom (to get it to actually honor the layer properties). Then if there are more than 50 fields you have to scroll through and turn them back on, because it restricts to 50 by default when you do that for some reason.

[L_OG]

Adding to this thread for documentation. I am observing the same issue in an Experience Builder web app.