# Feature or Bug - Collection issue? **URL:** \ **Category:** Ask for Help\ **Created:** [January 9, 2025, 5:34pm UTC](https://community.glideapps.com/t/feature-or-bug-collection-issue/79089 "2025-01-09T17:34:13Z")\ **Posts on this page:** 10\ **Page:** 1
**Author:** ![MattLB](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/mattlb/32/41284_2.png) [@MattLB](https://community.glideapps.com/u/MattLB)\ **Post date:** [January 9, 2025, 5:34pm UTC](https://community.glideapps.com/t/feature-or-bug-collection-issue/79089/1 "2025-01-09T17:34:13Z")
I changed a collection from List to Card and the action associated with it changed. In this case the action was supposed to update a single field in the User table. After changing from a List to a Card layout the action changed to overwriting ALL the fields in the user table row instead of a single column. I would think the action associated with a collection would stay the same no matter what the ‘look’ is. I think this is a BIG BUG…but maybe it is a feature that I never noticed before?? Here it is before: ![image](https://us1.discourse-cdn.com/flex002/uploads/glideapps/original/3X/7/d/7dcd06663292caebda315e8bd2b434292bb6bfd0.png) ![image](https://us1.discourse-cdn.com/flex002/uploads/glideapps/original/3X/c/f/cf8f3adb495092b646ee778ea0e8d1608dc02f62.png) And after: ![image](https://us1.discourse-cdn.com/flex002/uploads/glideapps/original/3X/9/8/98b115ae94bf321adf6c048dade9a99e71df587a.png) ![image](https://us1.discourse-cdn.com/flex002/uploads/glideapps/original/3X/6/a/6abf768f4e5be29fd34949f3b9f50a4e09a79503.png) ---
**Author:** ![MaximeBaker](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/maximebaker/32/80877_2.png) [@MaximeBaker](https://community.glideapps.com/u/MaximeBaker)\ **Post date:** [January 9, 2025, 5:49pm UTC](https://community.glideapps.com/t/feature-or-bug-collection-issue/79089/2 "2025-01-09T17:49:49Z")
Mmm… Sounds like a bug yes. But it some cases, it is maybe doing that to prevent errors when changing layout. ---
**Author:** ![MattLB](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/mattlb/32/41284_2.png) [@MattLB](https://community.glideapps.com/u/MattLB)\ **Post date:** [January 9, 2025, 6:01pm UTC](https://community.glideapps.com/t/feature-or-bug-collection-issue/79089/3 "2025-01-09T18:01:02Z")
I changed from a List to a Card, which I have done many times when exploring what looks correct for the data type. I do not remember the action being reset each time I did this. In this case since I was updating a field in the User table (a single column/field) and Glide reset all basic fields/columns for this row which was problematic. Just happy I caught it. If this is the expected behavior a warning should appear that your actions will be reset. I can create a BUG report if needed since I can easily re-create and record via Loom or Tella. Thanks ---
**Author:** ![MaximeBaker](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/maximebaker/32/80877_2.png) [@MaximeBaker](https://community.glideapps.com/u/MaximeBaker)\ **Post date:** [January 9, 2025, 6:02pm UTC](https://community.glideapps.com/t/feature-or-bug-collection-issue/79089/4 "2025-01-09T18:02:14Z")
Yes, I think you should do that 🙂 Thanks! ---
**Author:** ![ThinhDinh](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/thinhdinh/32/49_2.png) [@ThinhDinh](https://community.glideapps.com/u/ThinhDinh)\ **Post date:** [January 10, 2025, 12:48am UTC](https://community.glideapps.com/t/feature-or-bug-collection-issue/79089/5 "2025-01-10T00:48:55Z")
> [@Hard to recreate: Set-Column-Values resets to default 'randomly'](https://community.glideapps.com/t/hard-to-recreate-set-column-values-resets-to-default-randomly/76517): > > 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 fe… I recall this being familiar, and I think you reported somewhat the same bug yourself here. ---
**Author:** ![ThinhDinh](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/thinhdinh/32/49_2.png) [@ThinhDinh](https://community.glideapps.com/u/ThinhDinh)\ **Post date:** [January 10, 2025, 12:53am UTC](https://community.glideapps.com/t/feature-or-bug-collection-issue/79089/6 "2025-01-10T00:53:01Z")
Also, this is still a bug, but generally I just use a “named” action in these cases to save the headache, it’s also much more manageable down the line when you have a lot of actions. If you set it up like this, these actions won’t show up in the Workflows page, and are not reusable in other places. ---
**Author:** ![Darren\_Murphy](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/darren_murphy/32/47326_2.png) [@Darren\_Murphy](https://community.glideapps.com/u/Darren_Murphy)\ **Post date:** [January 10, 2025, 3:01am UTC](https://community.glideapps.com/t/feature-or-bug-collection-issue/79089/7 "2025-01-10T03:01:22Z")
Absolutely, 100% agree. This is best practise. ---
**Author:** ![MattLB](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/mattlb/32/41284_2.png) [@MattLB](https://community.glideapps.com/u/MattLB)\ **Post date:** [January 10, 2025, 6:48am UTC](https://community.glideapps.com/t/feature-or-bug-collection-issue/79089/8 "2025-01-10T06:48:00Z")
Dang you guys are good. Thanks for the assist. ---
**Author:** ![MattLB](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/mattlb/32/41284_2.png) [@MattLB](https://community.glideapps.com/u/MattLB)\ **Post date:** [January 10, 2025, 3:10pm UTC](https://community.glideapps.com/t/feature-or-bug-collection-issue/79089/9 "2025-01-10T15:10:56Z")
I think my title was correct - this Glide Feature exists cause it was not considered a bug when it was reported FOUR months ago (by many uses in many different contexts). The feature is Glide ‘guesses’ what you are trying to do and ‘helps’ by auto-populating ‘direct’ actions. In these examples by deleting the developers work and rewriting it with what Glide _thinks_ will ‘help’. I never filed it as a formal BUG so it just went away…but I bet it is still biting other users and causing hours of code review/debugging. At minimum a warning should pop up when changing styles with direct actions already set. (@ThinhDinh @Darren_Murphy are correct - Always Use Workflows A-U-W) @david - I think Glide ‘guessing on actions’ should be a thing of the past. It may have been appropriate when Glide first started, but it has outlived its purpose and Glide has has an alternative - AI. ---
**Author:** ![system](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/system/32/53398_2.png) [@system](https://community.glideapps.com/u/system)\ **Post date:** [January 17, 2025, 3:11pm UTC](https://community.glideapps.com/t/feature-or-bug-collection-issue/79089/10 "2025-01-17T15:11:11Z")
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.