Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
C
Core
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 913
    • Issues 913
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Operations
    • Operations
    • Incidents
  • Analytics
    • Analytics
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
  • Development
  • Core
  • Issues
  • #1849

Closed
Open
Opened Jul 02, 2020 by justinfreeman (Agileware)@justinfreeman🚴🏿Developer

Smart Group search criteria cannot be saved if the pre-existing Smart Group search criteria returns no results

Smart Group search criteria cannot be saved if the pre-existing Smart Group search criteria returns no results.

This is increasingly common since CiviCRM will now warn users about disabled/deleted custom fields and the related Smart Group that need to be updated. The user is then stuck and unable to action the warning notice displayed by CiviCRM.

chrome_aphUhSKcqb

A workaround to the problem is to manually add a contact to the Smart Group and then the ability to update the Smart Group via Actions becomes available. Or to change the search criteria so that it does return results - even if those results do not match the purpose of the Smart Group. These workarounds are not obvious to end-users.

It would be preferable for the action to update the Smart Group criteria was available even if no search results were returned by the current search, allowing the user to save the search criteria. This gives the future ability for contacts that match the search criteria to populate the group.

chrome_DIjHo5MOpZ

Relates to #1471

Agileware Ref: CIVICRM-1509

Edited Jul 02, 2020 by justinfreeman (Agileware)
To upload designs, you'll need to enable LFS and have admin enable hashed storage. More information
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: dev/core#1849