Hard to recreate: Set-Column-Values resets to default 'randomly'

Documenting process of complex BUG interaction.

I created two collections based on the same underlying query: one a card and the other a table. The end user can view the data based on their preferences (as a list or as a card). I use visibility to show/hide the collection.

I used a Title action button to “set col vals” with the User table whole row selected. I updated ONE text column (CM View-AS) to “CARD/TABLE” in the User table.

I double/triple checked this was correct and tried it out a few times.

NOTE: I did this because somehow (using the same procedure described above) the set-col-val action had updated ALL FIELDS IN THE User table about an hour ago. I had to fix this (which meant going to the Google table) because somehow Glide auto-populated the set-col-val with table data that I did not select.

Back to the process: I did not have the title set for this collection so I updated it with a template column from my collection.

When I tested the collection ‘switching’ I lost all my User data because Glide overwrote/reset my set-col-val after I changed the Title which ‘reset’ set-col-val to update all text fields in my User table - NOT JUST THE ONE FIELD I was updated.

The only column I updated was CM View-AS but this is what it looks like:
image

image

I guess it’s a case of Glide wrongly resetting the configurations of your set column values action to their “best guess” version (i.e what they think is the best value to set to a column, upon creating the action).

If you can reproduce this, sounds like you should be submitting a ticket. But as you said it’s hard to reproduce now.

Came here to report this too! This caught me out on an app where it re-set a bunch of user profile values! Luckily I was working in my own user profile and noticed before publishing or it could have been really detrimental. Seems to be re-createable for me when going from Card View to List View. Interestingly, you can undo it, but it takes 6 clicks of the undo button to reverse it.

Screen Recording

2 Likes

Probably exactly what I was doing (alternating between CARD and LIST views) but didn’t know the exact root cause.

Thanks…I think this is a bug too. And I should have used UNDO a few times versus clearing a lot of columns in the set-col-vals action.

I experienced this Bug in Glides AI Builder.

Seems to be when switching between the Old List Collection Style and any other Style! Worth double checking your actions when you change Collection Styles.

1 Like

Is this officially a bug now? Thanks to all the feedback from Gliders!