Hi - Is it possible to set visibility settings using multiple values. For example if there is a drop down (8 values) field which should be visible for only 3 values.
Any kind special character can be used?
Workaround can be grouping them but wanted to know if anyone used multiple entries for visibility.
Thanks
Well, straight answer is No. Only one condition is allowed to change visibility. But I managed to create a minor workaround for it on my app.It wasnât simple initially but it works well for my app.
So basically, I have a list of activities a user can choose and a âgreen checkâ has to appear on the activity if the user chooses the activityâŚalso only if the user belongs to a certain profile. (for ex, men cannot attend baby showers). So I added multiple âhollow checksâ to the list.
First criteria for the âhollow checkâ to appear is the profile criteria.One set of âhollow checkâ if user is male and a second set of âhollow checkâ if user is female. I then placed a âgreen checkâ next to it and changed visibility on selection. Needless to say, the âhollow checkâ would disappear if selected.
This worked for me only because I had only 2 conditions. I think for more than 2 conditions, I might have needed more hollow checks and the list would have been chaotic.
Hope to have helped.
@KNV you can âstackâ visibility rules by assigning them to layers and using grouping (1 viz rule per layer). I show how I use this technique in this video below to create a smart onboarding overlay for guiding new users through the steps in my app to get their first win. HTH. You can read a full write-up I did on this technique here.
Great post. Very clear and informative. Thanks!
This is Awesome!! it solved a big problem for me! Thanks 
cheers. glad it helped.
This group visibility solution doesnât seem to work with action buttons.
Action buttons will always be visible according to their own visibility rules regardless of the rules of the group they are part of.
Has anyone else run into this?
@grid7 - in your video it seems to show an option to âadd skills filterâ , similar to how it is available in the list settings. I am unable to find or see that option - when I am working to change visibility, I see only the 3 inputs as shown in the original post (dropdown to select variable, dropdown to select operator, and dropdown or input to add a single condition).
Whatâs going on here? Is there something Iâm missing?
Also, the solutions provided here (using layers with different visibility rules, using the transparent .png as in the video) provide a decent hack to make for âANDâ conditional visibility functionality, meaning you can set a component to be visible if ALL conditions are met. However, my specific use case requires an element to become visible if either of 2 conditions are met, basically an âORâ functionality. Is there any known way to accomplish this in Adalo?
Specifically - I have 2 fields in my âUserâ collection that define authorization for operating machinery - one field is âGeneral Authorizationâ, which defines whether or not they have received the general training and certification to operate the machines. A second field is âMachine Ratingsâ, which is a relational field to a collection of machines. This defines whether or not the user has been rated/authorized to operate a specific machine.
When viewing a Machine Profile, I want the user to see an alert that they are ânot authorized to operate this machineâ IF they are EITHER not generally authorized OR if they are not rated on that specific machine.
Any thoughts?
PS: @PrincipledPeter - I am not experiencing that issue when using âGroupsâ to add visibility layers. Buttons seem to be behaving the same behavior as any other component.
NOTE: I would wait to hear from @grid7 before you take my word for it, but I am suspicious that the video posted by him in this thread might be out of date - the âgroup layeringâ functionality to add multiple visibility rules is way cleaner and easier than putting in transparent pngâs, so Iâm thinking maybe that functionality didnât exist when the video was made.
Try using layers to stack visibility rules - you can select any element or existing group, click the 3 dots in the upper-right of the left panel, and select âMake Groupâ. You can make a group in a group in a group, and so on to infinity. And, each âgroupâ layer can have itâs own visibility rule. Note that, as I said above, in my experience this can only be used to give AND functionality on your rules, meaning all the rulesâ conditions must be met for your element to become visible. Donât know about getting some kind of âORâ functionality workingâŚ
(Edit - @PrincipledPeter I re-read your prior comment and realized you clearly said you WERE using the Group functionality to create visibility layers. my bad. Well, in that case all I can say is that I was not able to replicate the problem)
@tbtilton I made another thread about the problem with a cloneable app link: Group visibility when it contains action button
@PrincipledPeter yeah thatâs legit. I have to apologize, my comprehension skills seem to be on pause this morning. You clearly said âAction Buttonâ. In my apps, I was using just âbuttonsâ, and when I tested I just used a âButtonâ. Your cloneable app demonstrates the bug well, and I DID replicate the bug in my own app.
On an aside, is there any real difference between using an âAction Buttonâ and a âButtonâ, outside of some slight formatting differences? Furthermore, Is there any functional downside to just using an ellipse + Icon grouped to make an âAction Buttonâ? What is the component really for? Just a convenience thing for making an app quickly? Iâm curious because Iâve got hundreds of hours into building my app in Adalo and I literally never have used the âAction Buttonâ⌠even though I have a lot of things in my app that look like an âAction Buttonâ, and work like an âAction Buttonâ, I just literally have never used that component because it is super limited in terms of how it looks - canât modify the shadow, add border, etc.
Not an excuse for them to not fix the bug, but at least it SEEMS like this one has an easy work around: just donât use that component when you are layering visibility rules, use a regular button or a âcustomâ action button made from an ellipse+icon.
But yes - you are not crazy - this seems to be a bug 
Iâm not entirely certain but I think the action button floats always on screen regardless of scrolling while the regular button stays aligned to the other components on screen moves with the scroll.
Ah, yes. Seems that way. Another thing Iâve just done by anchoring my âalways on top/no-scrollâ buttons to the top or bottom of the screen.
That functionality probably has something to do with why itâs funky on itâs layered visibility rules. I know that the top/bottom anchoring system gets really weird with itâs behavior when you start having visibility rules mixed inâŚ
But, I do see the value in an easy âdrop-inâ button component that stays put w/r/t scrolling. Definitely easier than my top-bottom anchoring strategy. BUT, with that extra work, my buttons are customized and look wicked. haha.
Sorry to uselessly bump this post, but Iâm at a bit of a standstill until I can figure out if thereâs a way to run âORâ visibility logic on an element at this time or if I need to just do without. Anyone have any ideas? See my post from couple days ago for full explanation.
