1. Whenever a column is set to select, by default we show labels and not values.
2. For existing tables, since we have created this problem we ensure we don't break their apps. We will give an option called "Display As" as suggested in the original issue and for new select columns, it will be Label and for existing columns, it will be Value.
3. We make it clear that the computed value here refers to the default value/display value.
4. We make the select widget changes we did for options in the table and json form as well, create a new issue for this.
5. When the user has turned on server side filtering, we will ask the user to provide additional details for labels to be shown for cases where we cannot find them in options.
6. Depending on the "display as" property, we alter the search, sort and filter behavior accordingly.

@keyurparalkar @sbalaji1192

@dilippitchika I have raised a new feature request for point 4 mentioned above.

@rishabhrathod01 you think this is realted to #30074

Please, prioritize.
Wanted to use select in a table visualizing "labels" and using "values".
Thank you!

Hello!

I've created a public app to demonstrate a bug observed in the "gender" column. You can access the app here:
https://app.appsmith.com/app/select-in-column-bug/page1-65cee8067b1fda250a586c71?embed=true

The issue occurs when I attempt to edit a cell within this column and select a different option. Instead of displaying the labels "female" or "male", the cell shows the numerical values 1 or 2, respectively. Here's the data structure I'm using for the dropdown options:

[
  {
    "label": "female",
    "value": 1
  },
  {
    "label": "male",
    "value": 2
  }
]

I'm building an app where managers update client cities from a set list. This bug hurts a lot and makes updates with foreign key relations basically impossible.

Please, prioritize.
I have the same problem as [Scrafi4] .
Thank you!

I have the same problem.
Please, prioritize.
Thanks!

We had another customer hit this today.

I think we have a duplicate issue here: #21993

For context, see this screen shot. If I want to edit a field with a select, then I see the value (an id) as the default, but I can see the label when I'm selecting... but then once it is selected, I see the value again. This takes a very simple and powerful feature of the table, and makes it unusable.

In theory, I could parse the DB data, swap out the ids for the labels, and then try to swap them back again before saving to the DB... but this is incredibly messy. For now, it is best to use a JSON form for the editing, which severely limits the edit capabilities of the table row.

Looking forward for a fix :)

I would also like this to be worked on. I need my users to be able to select from just the label without seeing the value. Thank you.