# Strange button behaviour **URL:** \ **Category:** Report a Bug\ **Created:** [January 23, 2025, 6:10pm UTC](https://community.glideapps.com/t/strange-button-behaviour/79458 "2025-01-23T18:10:21Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![Simon\_Hill](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/simon_hill/32/94730_2.png) [@Simon\_Hill](https://community.glideapps.com/u/Simon_Hill)\ **Post date:** [January 23, 2025, 6:10pm UTC](https://community.glideapps.com/t/strange-button-behaviour/79458/1 "2025-01-23T18:10:21Z")
Is there an issue with Glide today? When I add a button component then change select an action the button disappears as if a visibility condition has been set. Doesn’t matter what action I select or de-select, the visibility does not return… I thought I found a workaround by adding a button block with 2 buttons then deleting the 2nd. However, this soon disappeared too this time triggered by me changing to view the App as another signed-in user. Very strange. ---
**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:** [January 23, 2025, 7:01pm UTC](https://community.glideapps.com/t/strange-button-behaviour/79458/2 "2025-01-23T19:01:42Z")
Is your screen connected to a row? ---
**Author:** ![Simon\_Hill](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/simon_hill/32/94730_2.png) [@Simon\_Hill](https://community.glideapps.com/u/Simon_Hill)\ **Post date:** [January 23, 2025, 7:04pm UTC](https://community.glideapps.com/t/strange-button-behaviour/79458/3 "2025-01-23T19:04:55Z")
Not really. I have it connected to a table with row owners. However, I realize now that with a new owner, the table not have any rows that are visible to a new user. Hence, any button actions that use a row from the current table will not be valid. I wanted to just open a new screen that would manipulate data in the users table. But it seem this is problematic for Glide when the screen’s table is blank. UPDATE: It is solved by specifying the Data for the action comes from a different table. Not sure if this is a new feature in the last few months. I never realized you could do this and always left that as default. ![image](https://us1.discourse-cdn.com/flex002/uploads/glideapps/original/3X/0/b/0b5ac40ea85776c8e3dced3d7f6afa9015bd2fb0.png) ---
**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 24, 2025, 7:37am UTC](https://community.glideapps.com/t/strange-button-behaviour/79458/4 "2025-01-24T07:37:23Z")
> [@Simon\_Hill](#): > > It is solved by specifying the Data for the action comes from a different table. Not sure if this is a new feature in the last few months. I never realized you could do this and always left that as default. No, that’s not new. It’s been an option for as long as I can remember. It’s commonly used with custom forms - open a new or details screen via a Single Value column in the User Profile row that targets a single row helper table. ---
**Author:** ![Simon\_Hill](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/simon_hill/32/94730_2.png) [@Simon\_Hill](https://community.glideapps.com/u/Simon_Hill)\ **Post date:** [January 24, 2025, 8:52am UTC](https://community.glideapps.com/t/strange-button-behaviour/79458/5 "2025-01-24T08:52:40Z")
Ok my Alzheimer’s must be new! 🙂 ---
**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 31, 2025, 8:52am UTC](https://community.glideapps.com/t/strange-button-behaviour/79458/6 "2025-01-31T08:52:40Z")
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.