Answers.Body: <p>If this is a one off exercise, you can use the advanced search to select all the contacts are in any group (just keep adding all your groups to the group selection box) and create a new group "in any group". Then use the include/exclude custom search to exclude all the contacts on the "in any group" group. Then you can add them to a "not in any group" group.</p>
  
  <p>Actually you could probably do it straight from include/exclude custom search.</p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2019-09-16T21:15:10.323Z
Answers.Text: Did you mean "include/exclude custom **search**"?
Answers.UserDisplayName: Demerit
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2019-09-16T21:29:28.227Z
Answers.Text: Yes - corrected
Answers.UserDisplayName: Mick Kahn
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2019-09-17T15:48:20.920Z
Answers.Text: Going straight to a custom Include/Exclude Search did the trick—thanks, Mick. Now, should I report as a bug the error message I get when I set the Group(s) filter to 'Is Empty' in the Constituent Summary and Search Builder pages?
Answers.UserDisplayName: John Mark
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2019-09-17T16:00:47.097Z
Answers.Text: Glad that worked. I'm not sure its really a bug. From what I can see the operator list is the same for all fields and only some of those make sense and some don't for different types of field. I think it would be a major development to clean this up to be foolproof, not a simple bugfix.
Answers.UserDisplayName: Mick Kahn
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2019-09-16T20:27:27.070Z
Answers.LastActivityDate: 2019-09-16T21:29:14.367Z
Answers.LastEditDate: 2019-09-16T21:29:14.367Z
Answers.UserDisplayName: Mick Kahn
Body: <p>Civi 5.15.1, Wordpress 5.2.3</p>
  
  <p>I'm trying to get a list of all contacts who are not in any group (Smart or otherwise). I've done this two ways, with the same result: the first is by filtering the Constituent Summary report, and the second is using the Search Builder.</p>
  
  <p>In either case, when I set the Group(s) filter to 'Is Empty', I get this message: "Sorry, due to an error, we are unable to fulfill your request at the moment. You may want to contact your administrator or service provider with more details about what action you were performing when this occurred."</p>
  
  <p>And when I set the Group(s) filter to 'Is Null' (available via Search Builder only, not the report), the resulting list includes contacts who are in Smart Groups, whom I want to exclude.</p>
  
  <p>I'd prefer not to use the Import Contacts workaround provided by Nicholai here:
  <a href="https://civicrm.stackexchange.com/questions/2169/how-to-find-contacts-with-no-group">How to find contacts with no group?</a></p>
  
  <p>And @Xavier's extension based on it does not seem to be available anymore
  (<a href="https://civicrm.org/extensions/lonesome-find-contacts-without-group" rel="nofollow noreferrer">https://civicrm.org/extensions/lonesome-find-contacts-without-group</a>).</p>
  
  <p>Does anyone have any other ideas? Thanks!</p>
  
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2019-09-16T21:16:07.470Z
Comments.Text: Don't know if it still works but the extension mentioned is here: https://github.com/TechToThePeople/lonesome
Comments.UserDisplayName: Demerit
Tags: <groups><smartgroups>
Title: how to retrieve non-grouped contacts?
ThreadText: # how to retrieve non-grouped contacts?
  
  (Asked by: username_0 on 2019-09-16)
  
  Civi 5.15.1, Wordpress 5.2.3
  
  I'm trying to get a list of all contacts who are not in any group (Smart or otherwise). I've done this two ways, with the same result: the first is by filtering the Constituent Summary report, and the second is using the Search Builder.
  
  In either case, when I set the Group(s) filter to 'Is Empty', I get this message: "Sorry, due to an error, we are unable to fulfill your request at the moment. You may want to contact your administrator or service provider with more details about what action you were performing when this occurred."
  
  And when I set the Group(s) filter to 'Is Null' (available via Search Builder only, not the report), the resulting list includes contacts who are in Smart Groups, whom I want to exclude.
  
  I'd prefer not to use the Import Contacts workaround provided by Nicholai here:
  [How to find contacts with no group?](https://civicrm.stackexchange.com/questions/2169/how-to-find-contacts-with-no-group)
  
  And @Xavier's extension based on it does not seem to be available anymore
  (<https://civicrm.org/extensions/lonesome-find-contacts-without-group>).
  
  Does anyone have any other ideas? Thanks!
  
  **Tags:** groups, smartgroups
  
  > **Comments:**
  > **username_1**: Don't know if it still works but the extension mentioned is here: https://github.com/TechToThePeople/lonesome  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_2 on 2019-09-16. Score: 4 | Accepted answer
  
  If this is a one off exercise, you can use the advanced search to select all the contacts are in any group (just keep adding all your groups to the group selection box) and create a new group "in any group". Then use the include/exclude custom search to exclude all the contacts on the "in any group" group. Then you can add them to a "not in any group" group.
  
  Actually you could probably do it straight from include/exclude custom search.
  
  > **Comments:**
  > **username_1**: Did you mean "include/exclude custom **search**"?  
  > **username_2**: Yes - corrected  
  > **username_0**: Going straight to a custom Include/Exclude Search did the trick—thanks, Mick. Now, should I report as a bug the error message I get when I set the Group(s) filter to 'Is Empty' in the Constituent Summary and Search Builder pages?  
  > **username_2**: Glad that worked. I'm not sure its really a bug. From what I can see the operator list is the same for all fields and only some of those make sense and some don't for different types of field. I think it would be a major development to clean this up to be foolproof, not a simple bugfix.  
  
  ---
  
  