Conditionals & search in "All searchable fields" in user list

This is something i am also looking into. I have around 125 fields, while the searchable fields of a group are finally around 10 or so.

My fields are being published on a tab while the tab is conditioned to a specific user group. If i am doing a conditional for list search, will this work out or will it conflict with the conditional tab, and can i hide the field, showing all lists as well?

Tab conditions will not work for userlist searching. Only field conditionals can work in userlist searching.

I forgot: It would be brilliant, if i could sort the fields too, which i condition to be shown on the search list form.

On userlist searching specifically, no. Field order in searching is based off the order of your tabs and then the fields on those tabs.

Let me be clearer about the problem:

User A from usertype A has - among others - "unique" fields, which are hidden in profiles of usertype B with conditionals.

Now, User B shall be able to search in all fields that are searchable (shared [A&B] & unique) WITHOUT these fields appearing as searchable on the List with Usertype B in reverse.

Difficult to explain but hope I was clear...

We are matching Host Families with Au pairs (like a dating website, e.g.) but the profile fields of the 2 groups differ considerably.

Got that. But may i suggest something: I'd like to have a dropdown option additionaly to entering text. If i have provided a dropdownlist, which entries are being used as a conditional, i have to pin that down each and everytime, making sure, that i do not create typos and have finally problems within the condition i might not even think of. So, it would be great, that, if you select a dropdown/select/multiselect field, you can use one or more of that entries without having to write them down. Which is a pain with hundreds of fields, you create conditions for userlists etc.

Will conditional fields for search use interfere with conditional tabs?
If i create a condition, where a specific field will show on Userlist search; and also on one specific TAB, do i create a conflict on that one? Should know, before i am going to condition them all =

I made the following. I have several user groups, whereas each usergroup has a bunch of fields, not common with the other groups. This fields i have placed on according conditional tabs. If i have a tab, which is conditional for two or more usergroups i use REGEX to show them on more than one group's profile.

I also managed to show the fields to the public, i.e., if you are in group 1 and view a profile of group 2 you will see that profile's tabs.

I made here a mistake. I logged in as usergroup's 1 user, and couldn't see usergroup's 2 user's profiletab with usergroup's 2 fields.

Invested several hrs and made Kyle mad, until i found out, it was a setting problem. I haven't had filled in the user's specific profiletab fields and the overall setting was: Do not show empty fields. Since i didn't fill in any groupspecific field, it didn't show the tab, which made me crazy.

Complex, as CB is, this happens sometimes.

The only way to have specific fields searchable on a userlist is to not display every searchable field and only allow searching what is actually on the userlist. Your only alternative is to condition a field search display using CB Conditionals in a field conditional.

CB Conditionals can change whether a field is searchable or not, but only using Field conditionals. Tab conditionals can not do this.

Tab and Field conditionals can't conflict with one another. Field conditionals can conflict with other field conditionals and tab conditions can conflict with other tab conditions though so have to be careful with conditioning a tab or a field multiple times on the same displays (those under "For...").

krileon wrote: The only way to have specific fields searchable on a userlist is to not display every searchable field and only allow searching what is actually on the userlist.

Not sufficient in the described use-case.

krileon wrote: Your only alternative is to condition a field search display using CB Conditionals in a field conditional.

That does not work as expected. Fields are conditioned correctly on profiles - surprisingly activating the conditionals for list-search has the reverse effect. They are being hidden. Also creating "reverse" conditionals in addition with just "list-search" activted fails.