Feature or Bug - Collection issue?

[MattLB]

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:

And after:

[MaximeBaker]

Mmm… Sounds like a bug yes. But it some cases, it is maybe doing that to prevent errors when changing layout.

[MattLB]

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

[MaximeBaker]

Yes, I think you should do that

Thanks!

[ThinhDinh]

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 fe…

I recall this being familiar, and I think you reported somewhat the same bug yourself here.

[ThinhDinh]

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.

[Darren_Murphy]

Absolutely, 100% agree. This is best practise.

[MattLB]

Dang you guys are good. Thanks for the assist.

[MattLB]

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.