If you make all columns editable for the table, all the changes will be inside the "changesetArray".
From here, it would be a matter of making the request to update such entities. But doing it from the zoomed in view is a different story, because the changeSetArray and changeSetObject are read-only.
For example, if we make the text input of the zoomed in view reference the changeSetObject (no iteration needed on the object => better performance) :
There is no way that changing the input will change the values on the changeSetObject (or array).
For example:
A workaround I can think for your use case is to use a separate object to keep track of the changes made on the zoomed in view, like "localStorage" or a state variable with the value of an object. We could add key-value pairs, where the keys are ids of the entities, and the values are changes made on the zoomed in view. This should work, but the changes won't be visible on the table until we run the update query.