CiviCRM Views Smartgroup
This is a Drupal module that attempts to expose CiviCRM group contacts to Drupal Views for both regular and smartgroups.
Currently, CiviCRM exposes group contacts to Drupal Views for regular CiviCRM groups. However, smartgroup contacts are built 'on the fly' and are saved in a cache table that is separate from the
This module uses a third table that merges contact from both the regular group contact table and the smartgroup cache table using two methods. The simple method uses a mysql view table: this is a robust implementation that is suitable for smaller numbers of a group contacts. The complex method uses triggers and the Drupal cron to create emulate a materialized view, and while less robust is necessary for larger databases.
The simple and complex versions are available as separate branches. If switching between these, ensure to fully uninstall each module first and confirm that the respective
_civicrm_group_contact_cache table (or view) has been deleted.
Caveats and known issues
- The Drupal cron needs to be regularly run so as to rebuild the
civicrm_group_contact_cachetable for all smartgroups.
- In general, the
civicrm_group_contact_cachetable won't be rebuilt except when the Drupal cron is run. This means there is the potential for group contacts to appear empty or to be stale. However, by using a group ID in the Views argument or filter, or the group name in the Views filter, this will cause the cache to be updated for that specific smartgroup.
Caveats and known issues for the Complex version
- The initial implementation of this module was to use to use a mysql view to dynamically merge both the regular and smartgroup cache tables. However, mysql does not have the option for materialized views and so with large numbers of contacts, querying this table became prohibitively expensive. Instead, we have had to use a regular mysql table for which it's our responsibility to keep up to date. Which leads us to...
- We use triggers on the
civicrm_group_contact_cachetables to keep the merge table up to date. However, except in the very latest versions of mysql, only one trigger is allowed to be attached to a table at a time — which means we need to replace the CiviCRM logging triggers if logging is enabled. Therefore, logging will be disabled for group contacts.
- If logging is enabled, CiviCRM will attempt to wipe our triggers periodically and replace with its own. This means the merged table can become stale unless the Drupal cron is regularly run.
- The Drupal cron needs to be regularly run. This cron will 1) rebuild the
civicrm_group_contact_cachetable from the smartgroups definitions for all groups 2) repopulate the merge table with contact data and 3) reattach triggers to the
civicrm_group_contact_cachetables (which may no longer exist thanks to CiviCRM logging).