Yes, that is current default behavior because it will be very tricky if you want the system update each of your existing registered user profile data once admin added new custom field into user workflow, it will be hit timeout error imagine if the site has a lot of users.

If you want your existing registered user to fill in those new custom field, I would suggest you this way :

1. Enable this setting from backend > Easysocial > Setting > Users > General > Profile Completion Checks

2. Enable this setting from backend > Easysocial > Setting > Users > General > Action On Incomplete Profile - Redirect to edit profile page https://take.ms/jnHot

3. So when you added a new custom field, it will redirect user to edit profile page to fill in that new field then they only can access other page.

Hello Arlex,

thank you for your answer, i am wondering, what exactly happens, if somebody is searching for a field, that has been added later. Search is recognizing, that there is no value in the field, because the field does not exist in this profile till first saving. So if there is a field, you can search, it seems to exist this field, then if there is a profile, that returns no result for this search, the field is likely supposed to be empty. So why not showing this field as empty?

I tried the profile completeness check, but unfortunately we have some tabs in profile and if a user clicks to complete its profile, you are directly in editing mode of first tab. This is irritating because more likely the missing values are in other tabs in our case. So it would be helpful, if this link would go to the profile at all and then one could click the specific tab to complete the profile.

Thank you and best regards

thank you for your answer, i am wondering, what exactly happens, if somebody is searching for a field, that has been added later. Search is recognizing, that there is no value in the field, because the field does not exist in this profile till first saving. So if there is a field, you can search, it seems to exist this field, then if there is a profile, that returns no result for this search, the field is likely supposed to be empty. So why not showing this field as empty?

I am sorry that I still feel lost here, do you mean those new custom field you add, it shouldn't show it from the "select field" selection field under advanced search page https://take.ms/W8k1u? Because when the user trying to search those new field under advanced search page, it will always show empty result since user haven't save the profile yet.

Am i understand correctly?

do you mean those new custom field you add, it shouldn't show it from the "select field" selection field under advanced search page https://take.ms/W8k1u? Because when the user trying to search those new field under advanced search page, it will always show empty result since user haven't save the profile yet.

No, it should show in search, but a search should give me an empty result, if field has not been saved yet. At the moment it does not work as you say in bold text, instead a search is absolutely ignoring these fields. In a specific search result the field is neither empty nor not empty. So what one would expect, that a result of such fields would be empty instead of non existant.

Thank you and best regards

Hey there,

I am really sorry for the delay of this reply as it is a weekend for us here.

Maybe I list out 2 situation and see whether I still misunderstood as what you explained in earlier :

Situation A
---------------
1. I added a new custom field (checkbox) from my user workflow. (checkbox selection value: AAA, BBB, CCC)
2. Assuming user haven't save their user profile yet
3. Then someone trying to search this new custom field (checkbox) on advanced search page and the condition set to "is empty".

What result you expect to show regarding this situation A?

Situation B
---------------
1. I added a new custom field (checkbox) from my user workflow. (checkbox selection value: AAA, BBB, CCC)
2. Assuming user haven't save their user profile yet
3. Then someone trying to search this new custom field (checkbox) on advanced search page and the condition set to "is not empty".

What result you expect to show regarding this situation B?

Hello SI Support,

we have some custom fields in EasySocial. Multitextbox and Checkbox. Now if i am searching for a field the result of "is empty" + result of "is not empty" should be equal to total count of users (with no privacy). But there we have big differences.

Some of the fields have been added after adding the members. Now it seems, if an old member edits and saves his account, the new field is rated as empty or as not empty. But if an old member does not edit and save his profile, the field is handled, as if it would not be existent for the search. The Account does not seem to know, that there has been a field added.

Can you confirm this behavior? If so can you please provide a solution for this. Recent added custom fields should be handled as existent and empty for searching purposes.

Thank you and best regards

I think I had similar issues...try clearing the smart search index and re-index. Or try check the custom field UNIQUE KEY.

Hello Arlex, thank you for you answer and your examples.

Regarding Situation A, i would expect to find this user
Regarding Situation B, i would expect to NOT find this user

However, if i have 100 Users and a search for "is empty" shows me for example 40 users, i would expect a search for "is not empty" to give me a result of 60 users, because a field can only be empty or not empty.

Situation A
---------------
1. I added a new custom field (checkbox) from my user workflow. (checkbox selection value: AAA, BBB, CCC)
2. Assuming user haven't save their user profile yet
3. Then someone trying to search this new custom field (checkbox) on advanced search page and the condition set to "is empty".

What result you expect to show regarding this situation A?

Situation B
---------------
1. I added a new custom field (checkbox) from my user workflow. (checkbox selection value: AAA, BBB, CCC)
2. Assuming user haven't save their user profile yet
3. Then someone trying to search this new custom field (checkbox) on advanced search page and the condition set to "is not empty".

What result you expect to show regarding this situation B?

Regarding Situation A, i would expect to find this user
Regarding Situation B, i would expect to NOT find this user

However, if i have 100 Users and a search for "is empty" shows me for example 40 users, i would expect a search for "is not empty" to give me a result of 60 users, because a field can only be empty or not empty.

I will log this into issue tracker and see if we can find a better solution to approach this in next major release version.

Thank you Arlex, i am looking forward

You're most welcome.