# Bug in visibility on form **URL:** \ **Category:** Report a Bug\ **Created:** [December 23, 2019, 9:09am UTC](https://community.glideapps.com/t/bug-in-visibility-on-form/3093 "2019-12-23T09:09:15Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![mthakershi](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/mthakershi/32/1715_2.png) [@mthakershi](https://community.glideapps.com/u/mthakershi)\ **Post date:** [December 23, 2019, 9:09am UTC](https://community.glideapps.com/t/bug-in-visibility-on-form/3093/1 "2019-12-23T09:09:15Z")
Hello. There is definitely a bug in visibility condition module. See attached screenshot. ![Screen Shot 2019-12-23 at 2.34.31 PM](https://us1.discourse-cdn.com/flex002/uploads/glideapps/original/2X/1/16bcbd47e73ee1543e1011bfe9e5406e71c829dd.png) ---
**Author:** ![kyleheney](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/kyleheney/32/41173_2.png) [@kyleheney](https://community.glideapps.com/u/kyleheney)\ **Post date:** [December 23, 2019, 10:51am UTC](https://community.glideapps.com/t/bug-in-visibility-on-form/3093/2 "2019-12-23T10:51:52Z")
And/or in visibility?! That’s new (and maybe not working 100% yet). ---
**Author:** ![Jeff\_Hager](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/jeff_hager/32/43_2.png) [@Jeff\_Hager](https://community.glideapps.com/u/Jeff_Hager)\ **Post date:** [December 23, 2019, 1:53pm UTC](https://community.glideapps.com/t/bug-in-visibility-on-form/3093/3 "2019-12-23T13:53:09Z")
I think the problem is when you attempt the set a visibility condition (in edit mode) against a value that is not editable on the screen. I don’t think it’s an issue with the multiple conditions (at least I haven’t seen an issue yet). I did a little experiment where I set a visibility condition on a checkbox based on another value that is filled in the sheet, but not displayed on the edit screen. I set the condition to display the checkbox if the other value is not empty. Like you have observed, the condition seemed to react opposite of how I expected to. However, the condition started to work when I added an entry field for the value I was comparing against. I guess I would consider this a bug but as a workaround you could add an entry field for your ‘Type of Moment’, but set a condition on it that would cause it to never show on the screen. This will allow your other conditions to work while nobody will be able to change the ‘Type of Moment’. I assume that Glide isn’t pulling in values that don’t need to be updated and that is what’s causing the problem. You conditions are comparing against a blank value. My guess is that this is the same issue you are having in your other thread: [Possible bug in visibility condition](https://community.glideapps.com/t/possible-bug-in-visibility-condition/3041), but the problem there is that you are using a lookup column and cannot make the field editable for the workaround to work. ---
**Author:** ![mthakershi](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/mthakershi/32/1715_2.png) [@mthakershi](https://community.glideapps.com/u/mthakershi)\ **Post date:** [December 24, 2019, 6:42am UTC](https://community.glideapps.com/t/bug-in-visibility-on-form/3093/4 "2019-12-24T06:42:57Z")
You are rightly have “Expert” level 🙂 Worked perfectly in both my situations. So I added “Text entry” for the field I wanted to build condition on. Then set a condition so the field would never appear. After this, condition used in visibility worked as expected. Thanks a bunch. ---
**Author:** ![Michael\_Reinhart](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/michael_reinhart/32/2888_2.png) [@Michael\_Reinhart](https://community.glideapps.com/u/Michael_Reinhart)\ **Post date:** [May 14, 2020, 3:37pm UTC](https://community.glideapps.com/t/bug-in-visibility-on-form/3093/5 "2020-05-14T15:37:41Z")
Hi @Jeff_Hager, I have the same problem with my glide form where I have components set to be invisible if the number in a column (in the first data row) is greater then 0. I tried putting that that column in the form as a text label, text input and number input but the visibility function is still not reading it. I believe it is the same problem because the only time the component shows visible is if I set it to when the data field is empty. However, I even tried filling in every cell in the data column thinking it might be looking at a different row, but it still didn’t ready it. Here is the visibility condition ![image](https://us1.discourse-cdn.com/flex002/uploads/glideapps/original/2X/b/bfb97146506d783cdd20f4713d482b97929127cb.png) Here is the data column ![image](https://us1.discourse-cdn.com/flex002/uploads/glideapps/original/2X/2/26345919a19fb17be329b60dec9617133b88b880.png) The image component should be visible but it is not. Any advice would be greatly appreciated ---
**Author:** ![Jeff\_Hager](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/jeff_hager/32/43_2.png) [@Jeff\_Hager](https://community.glideapps.com/u/Jeff_Hager)\ **Post date:** [May 16, 2020, 1:42pm UTC](https://community.glideapps.com/t/bug-in-visibility-on-form/3093/6 "2020-05-16T13:42:36Z")
I think this will work if you create a column in your form response sheet that will capture the balance from the detail record where you have the form button. You can pass this value into the form using the Column Values. That will write it to the form response sheet, but also make the value accessible for your visibility condition without actually showing it on the screen. > **[Column values](https://docs.glideapps.com/all/reference/privacy-and-per-user-data/special-values/column-values)** > > Submit existing column values on behalf of the user. ---
**Author:** ![Michael\_Reinhart](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/michael_reinhart/32/2888_2.png) [@Michael\_Reinhart](https://community.glideapps.com/u/Michael_Reinhart)\ **Post date:** [May 17, 2020, 3:15pm UTC](https://community.glideapps.com/t/bug-in-visibility-on-form/3093/7 "2020-05-17T15:15:37Z")
That did it! Works perfectly now. You’re good @Jeff_Hager! Thank you for your quick response and help!!