# Visibility condition forms **URL:** \ **Category:** Ask for Help\ **Created:** [November 24, 2023, 3:01pm UTC](https://community.glideapps.com/t/visibility-condition-forms/68114 "2023-11-24T15:01:25Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![Ninjaaa](https://avatars.discourse-cdn.com/v4/letter/n/6f9a4e/32.png) [@Ninjaaa](https://community.glideapps.com/u/Ninjaaa)\ **Post date:** [November 24, 2023, 3:01pm UTC](https://community.glideapps.com/t/visibility-condition-forms/68114/1 "2023-11-24T15:01:25Z")
Heyy fellow Gliders! I’ve got a challenge app where the user shall submit a **picture** or **text** or **signature** as proof of having accomplished the challenge. I want to use a glide form for that. Since for every challenge a different proof is requested, I only want to show the specific entry field in the form (e.g. if a picture is requested as proof I only want the image picker field but make text and signature field invisible). The problem: The form is referencing to a table called “Challenge\_Log” but the information about which proof is requested is stored in the table “Challenges”. When configuring the visibility options, I can only choose columns from the “Challenge\_Log” table (which doesn’t make any sense). What can I do? I also tried to store the form information directly in the “Challenges” table with user specific columns. If I do that I can use the proof information from the Challenges table. But with submitting the form there is still created a new row (even though I put the after submit action to “set column values in this item”. Where’s my mistake… Can anyone please help… 😅 THANK YOU 🙏 ---
**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:** [November 25, 2023, 1:07am UTC](https://community.glideapps.com/t/visibility-condition-forms/68114/2 "2023-11-25T01:07:00Z")
You did not make any mistakes, @Robert_Petitto has asked for this before I believe (the ability to use conditions relating to the original table, rather than the destination). What I would do: - Create a JavaScript column that does some work with the “current URL” value. The point is to extract the rowID of the column you’re viewing. Do this in your user profiles table. - Create a relation from that to the rowID column in the “original” table. - Use a lookup to retrieve the proof required. - Use that lookup in your form. ---
**Author:** ![Robert\_Petitto](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/robert_petitto/32/25193_2.png) [@Robert\_Petitto](https://community.glideapps.com/u/Robert_Petitto)\ **Post date:** [November 25, 2023, 1:34am UTC](https://community.glideapps.com/t/visibility-condition-forms/68114/3 "2023-11-25T01:34:45Z")
Nice workaround ---
**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:** [November 25, 2023, 1:40am UTC](https://community.glideapps.com/t/visibility-condition-forms/68114/4 "2023-11-25T01:40:05Z")
Using a set column on entry to the row details view would also work, but the method above can save updates. ---
**Author:** ![Robert\_Petitto](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/robert_petitto/32/25193_2.png) [@Robert\_Petitto](https://community.glideapps.com/u/Robert_Petitto)\ **Post date:** [November 25, 2023, 4:40am UTC](https://community.glideapps.com/t/visibility-condition-forms/68114/5 "2023-11-25T04:40:06Z")
Oh, I meant putting it in the users table!