EnumList Column Width

[Jonathan_S]

Good Morning,

I have a Table thaqt has 2 columns that are EnumLists,
Issue is the Column with is staying very small, Just large enough for 1 item with a comma. I have the Table settings set to Wide, How can I force these columns to be wider to handle up to 3 items?

Thanks,

[Suvrutt_Gurjar · Accepted solution]

Please explore if below workaround helps.

If you wish to display handful of enumlist options, you may choose a longer heading for those enumlist columns in table view as the product name column in below example in image shows.

My testing had shown that the table view shows around 30-35 odd characters max. for a column content. However typically column heading also needs to be that longer for the text in records not to truncate.

So the enumlist column display name in the following example in table view is “-------------------------Product Name ----------------”

The dashes are introduced to display all the record contents for that column.

Please do perform a “Save and Verify” after the display name is changed and a couple of records are saved with longer contents in the enumlist column.

[Jonathan_S]

Perfect. Works perfectly.

Are there any future requests for having a more control over the column width?

[Suvrutt_Gurjar]

Good to know it works per your requirement.

On feature requests, I could not find an exact one that recommends changing the column header column length. I agree it will be useful to have continuous character length setting with some maximum limit instead of current three fixed options.

The below request is a similar one but not about length.

Capability to change size, color, etc of display name with format rule Feature Requests

The following discussion is from a year ago: I am reposting it as a “Feature Request” because I found myself wanting it again today. In the meantime, last year’s discussion contains a workaround.

[Bahbus]

To further on this subject a bit more, from previous conversations with devs and such, the Table View in general tries to anticipate the columns required width based on the contents already in said column. The downside being that if there are large fluctuations in the needed size per row, or if its the only row, AppSheet’s basically just guessing. Back when I used Table Views, my solution was to create 4 “invisible” rows with fake data at the maximum that I wanted the column to be, because my table was otherwise empty - and this table wasn’t meant to hold data long term. To make the rows invisible I just gave them all a key of 0 straight in the source, and create a slice for ID<>0, and ignore AppSheet’s warning about the duplicate keys.

AppSheet still reads the data and formats the column size for the view. I mostly did it this way because I really didn’t want to do the “------” thing and I was too lazy to experiment on whether or not copy/pasting specialty blank spaces would work (it does for certain ones).

Now I just do everything in my power to avoid Table Views whenever possible. They certainly have their place. But anytime I can find a more aesthetic view to use, I do. Example: my cart setup is a Parent detail view with an inline deck view for line items with a dynamic svg showing the price, use the summary section as the quantity. Bonus, I can choose to implement the swipe gestures. Granted, this only works for me because I only need to display exactly 4 pieces of information for each line item.