As you can see in the provided screenshot and example app JSON, when using a nested table, the "Row actions" expression's currentRow resolves to all the rows of the table, while the "Event handlers" scripts properly resolve the the specific row of the nested table.
Test (6).json (16.0 KB)
Hi there,
Thanks for reaching out! This is currently the expected behavior as the disabled field is mapped over all rows, so the evaluation popover shows the evaluated value of each currentRow. currentRow should still work as expected in the action's disabled field despite the confusing UI - we'll flag this to our team to see if we can make it more clear
