Can't use dropdown 'Select' column type in Table widget

antoine · January 25, 2023, 5:32pm

Hi, thanks for your app that’s very useful to build fast and simple GUI

I have a problem with a Select inside a table Widget. It seems that whatever I put in ‘Computed Value’, the ‘Evaluated value’ is always []. I don’t understand what is not done correctly.

I use Select widgets outside the Table, and it works fine.

This is the screenshot of the Select inside the Table :

This is the screenshot of the Select outside the Table, working fine :

Thanks for your help

Amelia · January 25, 2023, 5:48pm

Hello! Please try to use currentRow instead of selectedRow inside the table.
selectedRow returns the data of the row that the user clicked, while currentRow is referring to the row of the table that contains that particular cell that you are editing.

antoine · January 25, 2023, 5:59pm

Thanks for your quick reply.

Unfortunatly, I do want to choose the value in the selectedRow of another table in the page. Is it a problem to get the data from another table ?

But whatever I put in the Computed Value seems to be intepreted as [], see my next screenshot :

I don’t understand how can it be evaluated to []

Thanks again for your help

Amelia · January 25, 2023, 8:46pm

I could not reproduce this behavior. Could you please elaborate on your use case and explain what you would like to use in the Computed Value and in the Options for this select column? A loom.com screen recording would help us better understand the use case.

antoine · January 26, 2023, 11:35am

Oh, I was mixing up “Computed Value” and “Options” fields.

My usecase is pretty simple, I want the user to be able to add a row in the table, and for a specific field, I want the user to select an option from a list based on another table.
I did make it work, if I put the options directly in the “Options” field. But if I put a variable, it is always evaluated as ‘[]’.

It seems like a bug, like if it can’t evaluate a value for this options field inside a column of a table.

I could reproduce this behaviour with a minimal example app and produce a loom to show my problem : Loom | Free Screen & Video Recording Software | Loom

Tell me if you need more information

Thank you

Amelia · January 26, 2023, 4:07pm

Hi Antoine! I am still not able to reproduce this. Could you please share this example app with us? Please add support@appsmith.com as Developer and send us the link to the app.

antoine · January 26, 2023, 4:11pm

I added support@appsmith.com as a Developper in my sample app.

Here is the link: Appsmith

Amelia · January 26, 2023, 4:47pm

First of all, your table did not contain any Table Data, so this might be one of the things that are causing problems. Try binding it to a query.
Secondly, you’ll need to use {{SourceTable.selectedRow.choices}} and it should show the evaluated value correctly:

antoine · January 26, 2023, 5:37pm

My FinalData doesn’t contain any data because, in my use case, the user will populate entirely the table. But the my SourceData Table (in the example, data is written as raw text) is bind to a query.

Ok, indeed, if I put dummy values in my FinalTable, the options coming from my SourceTable are correctly evaluated when i click the field (in options). I do not understand why but that’s not what is important. But, even if it seems correctly evaluated, I still have ‘not found’ in the select dropdown, in the table.

See the first screenshot correctly evaluating my options: