Attribute table field name headings will not allow a font size smaller than 12?

Question

Type in anything less than 12 and it changes to 12.  Why?  WAB 10 was perfect.  Also note that changes the field name heading but not the text in the actual table for some reason.

Also when set to Use Layer settings it goes to alphabetical field name list which is not the layer settings.  When set to customize it flips back to the what the layer is but when you load the app it flips it back again.  We have way too many fields to reorder all of these.  They must match our schema.  Its always been layer order since the dawn of time.  Where is alphabetical coming from?

On top of all of that Drawing result from View in Table action always goes back to alpha!  No one wants alpha.  We had a committee pick the field order and we cant change it.

thanks

ChrisUnderwood · Answer

Hello @DougBrowning  ,  if it helps, this part "Also note that changes the field name heading but not the text in the actual table for some reason." is described in ENH-000147800, "For "Table" widget, a request to allow to change the font size of text inside the widget, configure the width of the fields columns and configure other elements inside the Table widget."

dougbrowning · Answer

Agreed the more we get into trying to migrate the apps the more baffled we get on how all this stuff made it through testing and development.  We see it right away so not sure why it was not addressed early but for sure it should have been addressed by now.  Esp things like locking font sizes - I have never seen another app do that in my life so just confused on why.  Someone added that code on purpose so it would be great to know the why.

I am going to keep posting these in the hope the team comes back to this board and starts tackling some of this stuff.

VenkataKondepati · Answer

Hi Doug,

Yes. I agree. We’ve been seeing the same quirks since moving away from WAB 10. That font size lock at 12 for attribute table field headers is definitely hardcoded in the newer widgets, and it’s pretty limiting when you’re trying to build clean, compact tables. Oddly enough, it only applies to the headers — the table rows still respect the text size settings.

As for the field order flipping to alphabetical, you're spot on — it should respect the layer’s schema-defined order, especially when "Use Layer Settings" is selected. What’s confusing is that the UI flips between alphabetical and schema order depending on whether you’re in the builder or live app. We’ve seen it too — feels like it’s caching or overriding somewhere in the config behind the scenes.

And yes — the “View in Table” action defaulting back to alpha is the most frustrating part. We’ve had schema-approved field orders as well, and manually reordering dozens of fields is not scalable or sustainable.

If you're working in Experience Builder or a newer version of Web AppBuilder Dev Edition, it may require diving into the JSON config and hard-setting the field order manually as a workaround — not ideal, but it sticks better than doing it through the UI.

I really hope Esri gives us back full control like we had in WAB 10 — or at least an option to lock field order to layer schema globally.

Regards,

Venkat