Table Edit behavior change?

Hello all!

My application has a table object with certain columns that are edit-able. I have a save function defined. There are no event handlers on the cells or rows. This has been working for quite some time with no issues, but today we noticed that when editing a cell in the table, the behavior has changed. If I choose one particular cell, make a change to it and then tab or click another cell, the "Save" function will either update both cells with the data I entered in only one cell, or attempt to update a cell that is not even edit-able and fail. The key note is that for success, you must keep your selector in only the cell you want changed - if you click, tab or otherwise move anywhere else in the table, the Save action will attempt to update the other cells as well. This was definitely not the behavior in the past. I did try searching for similar concerns but have not found anything recent. This was noted as of about 11:58 AM ET today, and was not a problem earlier this morning. I have not changed my application since last week.

Thank you for any advice.
Michael

Welcome to the community, @mhowellAI! Thanks for reaching out. :slightly_smiling_face:

We are currently investigating the root cause of this issue and will provide an update here as soon as it is resolved.

1 Like

+1 on this. I noticed that if I go to a different row it doesn't seem to happen, but that's obviously not a UX behavior I want to try to enforce...

Edit: also see this was reported in this post Table Edit behavior change?

Edit: and here? Bug Report on Table Component Save

Hey all - the fix for this rolled out with the release of Cloud version 3.185.0. Let us know if it's not working as expected!

2 Likes