Button Disappear

[Smarthome_Support]

Sorry I’m new to Glide, there some way can the button disappear after set the 2 column? like choose 2 product to compare and the button will disappear

[Darren_Murphy]

What is the action on the button?

Essentially you need to use the button actions to change a value in the database that can subsequently be used to drive a visibility condition or condition on the button action.

[Smarthome_Support]

I use add the row to the table

[Darren_Murphy]

So once two rows have been added, you want all the buttons to disappear?

[Smarthome_Support]

Yes because i just want to compare only 2 not more than that

[Darren_Murphy]

Okay, so what you can do is create a rollup column that counts the number of rows in your Compare Product table. Then set a visibility condition on your buttons such that they are only visible when the count is less than two.

That said, I’m fairly confident that this isn’t the right solution for your use case. For example, what do you expect to happen if multiple people are doing this at the same time? And what if a user changes their mind after making a selection? Or wants to make another comparison?

What I’m getting at here is that adding rows to a table is probably not the best approach. But I’ve just answered your question directly.

[Smarthome_Support]

Sorry, I’ have try and there some problem

1. the source is Spec table not Compare table
2. i just add the action button in the collection with source from Spec and add row to Compare
   So the visible condition is can not use is this case
   
   
   
   
   

[Smarthome_Support]

and I want to know if have multiple user in same time have the table will add from all user or only one by one

[schrutefarms]

I think if you look into using a Helper table in combination with User Specific Columns you would be able to build a solution that works better than this. Perhaps these resources can help you:

Helper Tables | Glide App Tutorial

How would you describe a helper table?

I use Helper Tables all the time. Most of my Glide Projects are littered with them. They have many uses, here are just a few examples: Reusable Custom Forms This is one I learned from @Jeff_Hager. The usual way to create a custom form is with a “Show Detail Screen → this item” action. This gives you a new details screen on your current row with a blank canvas, on which you then build out your form. However, another way to do this is by using a single row Helper Table. You create a Helper Table…

Unlock Personalized Data with User Specific Columns | Glide App Tutorial

Glide 101: Row Owners vs. User Specific Columns

[ThinhDinh]

I agree, I would just use a helper table with two choice components writing to two user-specific columns, and do lookups for comparison, perhaps.