# Glide STOP pre-populating the Set Column Value action

**URL:** <https://community.glideapps.com/t/glide-stop-pre-populating-the-set-column-value-action/83815>\
**Category:** Feature Requests\
**Created:** [August 13, 2025, 6:45pm UTC](https://community.glideapps.com/t/glide-stop-pre-populating-the-set-column-value-action/83815 "2025-08-13T18:45:13Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**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:** [August 13, 2025, 6:45pm UTC](https://community.glideapps.com/t/glide-stop-pre-populating-the-set-column-value-action/83815/1 "2025-08-13T18:45:13Z")

</div>

Please STOP pre-setting values for the Set Column Value. This is a horrible ‘best practice’ - better to do nothing than to ‘guess’ what a developer is trying to do. (PS. I usually use workflows for actions to avoid what just happened)

USE CASE:

I was testing a hierarchical display technique which involved writing temp values to the USER table. I was using a collection in CARD layout when I decided to look at the layout in LIST view (you know where this is going). When I clicked on the entry I knew immediately what happened when the entire APP went ‘blank’…..Glide had over-written the USER entry with random data.

I checked the Set-Row-Value and the 3 columns I was updating was reset by GLIDE to re-write all BASIC columns with “random” screen values.

Maybe 5 years ago this was ‘OK’ but this default action should be stopped immediately.