It's true - looking at the code, I can see that Search Builder expects an integer if you're searching on an integer field. An exception is made for using the IN operator, in which case it validates each value separately.
Trying to validate a regex to ensure it's non-malicious is a very difficult task, and I think the appropriate answer is to remove the ...
Note if you install from a tar file the extension is not available until 5.30. Git/composer/buildkit installs have it in 5.29.
Also the styling on the search page is messy until 5.31, and before then has some other issues.
UPDATE: As of 2020-10-06, it's now visible in the UI as an installable extension called "Search Kit" that comes included with 5....
There was a set of nasty bugs that fit the description of what you're talking about throughout 2015:
CRM-18435 in particular is getting a fix in the August 3rd release of CiviCRM. You can patch it now if you know how (patch is linked from the ticket above) ...
As @ErikH commented correcting the data format before import may be easier if %PAWS% doesn't work.
It looks like you're using ' - ' as your delimiter in that field, which appears to be a single value text field.
If you set this custom field as multiple value with a comma delimiter and import you would be able to use advanced search and your group values ...
The %PAWS% should work.
Another option is, which depends on the number of groups you have.
Export all people of group PAWS to an excel with a unique identifier (external id or email address for example). Import them and place all of them in right group.
You have to watch out using the search builder when your search involves related entities. Searching for does not equal X on something doesn't exclude contacts with a related entity with a field's value as X, it searches for contacts who have that related entity so long as the value doesn't equal X.
In other words, searching for contacts where tag name ...
While a code-level fix is obviously preferable, the quick solution is to create two groups:
Everyone who attended the event who has the tag.
Everyone who attended the event.
Then use the custom search Include/Exclude by Group/Tag to include group 2 and exclude group 1. Who's left is everyone who attended without the tag.
Adding to the Suggestion of Jon G there is a simple extension to SearchBuilder that allows to paste ContactIDs into a separate field and converts those to an 'IN' query with comma separated values: https://github.com/bhahumanists/bha.searchbuilder
This is a recent bug introduced by the fix to a different search issue, issue #726.
A permanent fix will need to be found that doesn't break either scenario. However, to resolve your immediate issue, you can open file CRM/Contact/BAO/Query.php and delete line 3037.
I've reported this issue as #1048.
When you search for Group(s) Not In 2021_keep, Search Builder may be interpreting it as "contacts who are in some group that's not 2021_keep". That's not what you want.
Here are two three options for finding all the contacts who are not in the group "2021_keep".
Go to Search > Custom Searches and click on Include/...
It does sound like a reasonable feature request, and the good news is that it's already been implemented.
The pull request was merged in March, so any version of CiviCRM from 4.7.18 upwards should include it in the advanced search criteria.
I checked locally and here's a screenshot of the changed address fields in advanced search:
If you are not able find a search method that results in the people you want to add to a group. And you have a list of email addresses of the people in the group. You can use the import feature.
The import allows you to add contacts (newly imported or existing matched contacts) in to a group.
Contacts > Import Contacts ("For Duplicate Contacts" use Update)
In the advanced search under the "Address Fields" you can choose "Address Location" which defaults to primary only. By selecting all of them you can search by any address type. answer taken from this thread Using custom fields to store secondary addresses
This is job for the Search Builder that you can find in the Search menu
Select Individual Prefix
Complete with = and the desired title.
When the results are shown you can create a Smart Group for this search.
There was a small bug introduced in the last version where the calendar icon didn't show up in search builder date fields, but the actual datepicker still works fine.
The screenshots and videos are misleading, as they use Contact:Created Date as the example field - this is actually not a date field (despite the name) it is a Timestamp which doesn't work ...
In the documentation here https://docs.civicrm.org/user/en/latest/organising-your-data/smart-groups/#creating-smart-groups at step 6 it says it's a choice in the actions dropdown. If you don't see that option, check that you have CiviCRM:edit groups permission.
After you have made your advanced search and get no results, you will stay on the advanced search page.
If you look at the bottom of that page it will say "No matches found for:" and then list the options you have chosen. Can you see anything in there that wasn't related to the options you picked?
I only mention this as I have a similar problem and I can ...
In a stock installation of Civi 4.6, I don't think this is possible. However, this is possible in Civi 4.7: https://issues.civicrm.org/jira/browse/CRM-16137
This is a very simple patch, so if you want this functionality today, check this out: https://github.com/civicrm/civicrm-core/pull/5435/files
You've found a bug. Check out Reporting a Bug, starting with step 7.
As a point of interest - variations on this bug have been reported before. For instance, CRM-6652, several years ago, which was only fixed last month with CRM-16483.
If you're looking to patch this yourself, I would definitely look to CRM-16483 as a model.
I just tried to replicate this problem on the demo site but couldn't.
I would recommend upgrading to Civi 4.7.9, and if you still have the problem, you can do two things:
Try to replicate it on the demo server (demo.civicrm.org). If you can't, the issue is most likely in the configuration.
The "DB Error" isn't really enough info to go on. So you can go ...
The search builder should be able to give you this as it has a larger range of search operators available to you.
Head to Search > Search builder and then use the criteria:
Contacts > Current Employer ID > Is Null
That should return everyone who has no value for your current employer field.
Hope that helps!
Search Builder is more 'raw' and I find end-users are best to avoid it!
Search > Custom Searches > Include / Exclude Search will do what you want.
Once you have the results you could save it as a smart group for future use.
Search Builder seems to be broken for this functionality, you may report that as an issue in the issue tracker: https://issues.civicrm.org/.
My understanding is that you want to search within the backend of CiviCRM?
Using the API is currently probably the cleanest way of performing the search and adding them at once by using the Activity.get and chaining ...
It should be fixed in the latest rc (5.2) https://download.civicrm.org/latest
Was able to install the latest at this time, 5.1.2, and I am now able to query with the Search Builder for groups for the situation that was mentioned above.