Bug : Error in New Table component when using both AddRow and Update Row

Dear Retool Support Team,
I've encountered what appears to be a bug in the New Table component when simultaneously using AddRow and Update Row functionalities. Here's a detailed description of the issue:
When using both AddRow and Update Row in a New Table component, we can utilize two Save Event Handlers through the Table's Save Event Handlers: Save(Insert) and Save(Update). However, an error occurs during the initialization process when using the 'Clear changeset' or 'Cancel' button.
Specifically, if we use only the Update functionality and then attempt to Clear changeset, we encounter a "Table.insert_table.changeset update" error.
Steps to Reproduce:

  1. Set up a New Table component with both AddRow and Update Row functionalities.
  2. Configure Save Event Handlers for both Save(Insert) and Save(Update).
  3. Perform only an Update operation.
  4. Attempt to use the 'Clear changeset' or 'Cancel' button.
    Expected Behavior:
    The changeset should clear without any errors, regardless of which operations were performed.
    Actual Behavior:
    A "Table.insert_table.changeset update" error occurs when clearing the changeset after only using the Update functionality.
    This behavior seems inconsistent and appears to be a bug in the system. Could you please investigate this issue and provide guidance on how to properly handle this scenario or confirm if this is indeed a bug that needs to be addressed?
    Thank you for your attention to this matter. I look forward to your response and any potential solutions or workarounds.
    Best regards,

----Error Message------
Error: Cannot read properties of undefined (reading 'parm_key')
from insert_cmd_dtl.changeset update (insert_cmd_dtl)
from table2.newRows Update(table2)
from user interaciton

Hello @junhyeok!

Thank you for this detailed reporting of the issue and the steps to reproduce, it is very helpful for us.

Let me try to reproduce this and see if there is a work around or if I will need to file a bug report to our engineering team.

Can you share a screenshot of how you have you update row action set up?

For point 4, by 'clear changeset' button, did you re-name the save button that appears when you edit a row's value?

It looks like I am getting the same error, as my update query runs on save, and then tries to run again twice more and fails as the table's changeset array is emptied after the first update query runs and it cannot grab an ID :face_with_monocle:

Here is how I have my save action set up, is yours the same?