Hey @jignesh! So the .recordUpdates
property contains an entry for every column in your table - if any values have been updated (i.e. are editable in the table), those new values will appear in the property - if values havenāt been updated, then those non-updated values will appear. For a quick example, letās say I have a table with 3 columns, and I update two of them:
Iāve only updated the first two columns (I changed the customer ID to 645, and the store ID to 21) - the email column has remained untouched. Hereās what table1.recordUpdates
will evaluate to:

Youāll notice that even though we havenāt updated the email column, it still appears - we do this to make it easier to issue UPDATE
statements to your database / API. So if you wanted to issue an update query with this new data without using our SQL GUI, you could write something like this (depends on your SQL dialect, of course):
UPDATE your_table
SET customer_id = {{ table1.recordUpdates[0].customer_id }},
store_id = {{ table1.recordUpdates[0].store_id }},
email = {{ table1.recordUpdates[0].email }}
WHERE composite_key = whatever
Youāll notice that the email hasnāt changed, but weāre still including it here because it makes it easy to just have one update query that can handle any changes to your table (this query would still work if we only updated one column, or two, or three).
Note that if you update multiple rows then you can reference those updates via indexing .recordUpdates
at [1], [2], etc.
Hopefully this helps!