[Enhancement] Custom columns in table widget cannot reference other custom columns from currentRow

[sharat87]

Description

In the table widget, custom column can refer to other column values of the current row using bindings like {{currentRow.columnName}}. However, when using this to refer to other custom columns, the value always returns null.

If using other computed columns is not supported, then they should be removed from the auto-complete suggestions, or it gives the wrong impression that they can be used.

Steps to reproduce the behaviour:

1. Drop a new table widget.
2. Add a new column, the customColumn1, and set it's computed value to {{currentRow.step + 'x'}}. Notice that the values in this column show up correctly.
3. Now add another column, the customColumn2, and set it's computed value to {{currentRow.computedColumn1}}.
4. Notice that the value in this column is always empty.

Important Details

• Version: Cloud
• OS: macOS
• Browser: Firefox
• Environment: Production, https://app.appsmith.com.

[vicky-primathon]

@somangshu Will remove custom columns from auto suggestion. Since both customColumn1 and customColumn2 are function of primary column there definition can be written using primary column itself.

[Nikhil-Nandagopal]

@vicky-primathon @somangshu that is not a good solve. Custom Columns can be used as intermediate values. We should support this or let it live but not remove existing functionality

[somangshu]

@riodeuno this is also related to the custom table column which you were looking into this, Moved this to the needs info pipeline

[GreenFlux]

This feature would really simplify the JS needed to access a value from nested objects. I'm currently trying to pull a date value from order.line_items.properties and display it on the Order. I can easily parse out the date and display it in a table based on line_items but I can't reference that custom column in the parent orders table.

[somangshu]

Thanks for the context @GreenFlux, This is helpful, We are working towards a new version of this widget and we will keep this mind while implementing

[rohan-arthur]

confirming as per this slack conversation and forum this question, that referencing a custom column within itself also doesn't work - Please consider including this in the scope, or create a new issue for this.