Modifications to table's event handlers "deletes" all event handlers for table's columns and row actions

I have found myself somehow unable to make any changes to a table's event handlers without wiping out all event handlers on that table's columns and row actions :scream:

I happened to notice an "incomplete selection" on the table's event handlers, like so:

Screenshot 2025-01-14 at 4.09.02 PM

If I make changes to either of those two, even just as simple as deleting either of them, or trying to complete the incomplete entry, all the event handlers on columns in the table stop working, and all the row actions stop working too – because all the event handlers created for them literally disappear. Over a dozen of them. Yikes!

Before getting deep in the details on this, I'm mostly curious if anyone has encountered this kind of thing before?

1 Like

This issue is actually much worse than originally stated –

If I make modifications to the event handlers on any table in the (multi-page) app, it "disappears" all the existing event handlers on the columns and row actions for that table.

Even just adding a simple "Click Row - confetti" event handler to any table in the app nukes all the existing event handlers on the columns and row actions for that table.

1 Like

I ran into this issue yesterday as well. It keeps wiping all my event handlers throughout my table (cell clicks, row actions, table events, etc)

Sorry to hear it's affecting you as well, but at the same time, I'm also glad I'm not the only one. I've already expended too much time on this, most of which was simply trying to deduce what was causing all my events to stop working. I even rolled back to a previous release hoping that might fix it (it didn't). I'm trying to refine some existing functionality, and add more too, and this bug is effectively preventing that from happening.

Yeah super frustrating. I opened another topic + emailed their support in an effort to get an expedited response.

1 Like

Hi there! I'm looking into this - I will keep you posted on any follow up questions or updates

2 Likes

Hi everyone -- thanks for your patience! This issue should be fixed now.

1 Like