[Feature]: Set table columns isEditable property programmatically.

[dixerus]

Is there an existing issue for this?

• [X] I have searched the existing issues

Summary

Allow setting column tables isEditable property in code.

Why should this be worked on?

There are use cases where table columns are dynamic. An ability to set column properties (in this case, isEditable) on the fly in code helps make these use cases possible.

[mschuelein]

Just ran into this problem today, good to see that there's already an issue open.

My use case is: I want to show data of multiple database schemas and instances in one table. Users have to be able to send queries, to get data from different tables. So the columns will always be different, depending on the table that's shown.

[dilippitchika]

Thanks for adding this information @mschuelein, can i ask why you are showing data from multiple instances in one table? Do the queries vary a lot?

[mschuelein]

Thanks for adding this information @mschuelein, can i ask why you are showing data from multiple instances in one table? Do the queries vary a lot?

Hey @dilippitchika, thanks for asking. We want to show data from multiple instances, because we want an easy to use solution for our non technical team members. So they dont have to run queries on 3 different connections 3 times, just one at a central place. The data structure of the instances will always be the same. And the queries can be any form of CRUD statement, against any table or view in our data structure. We also dont want to implement the structure manually in Appsmith, because then we would have to do changes here for every change we do to our data structure.

[mschuelein]

Is there any update on this? Would be really appreciated, because it limits our possibilities to use Appsmith properly.

[dixerus]

Update?

[keyurparalkar]

Thanks for showing interest in this feature. We will check this with the team internally and get back on this here.