Views3 Integration

Drupal 7

These instructions assume CiviCRM and Drupal are on separate databases located on the same physical host. If your CiviCRM and Drupal are located within the same database the 12 steps below are not required.

  1. Before making any changes, it is strongly advised that you make backups of your mysql databases and settings.php file.
  2. If you have different database users for your CiviCRM and Drupal databases, then you need to grant SELECT access for the Drupal user to all the CiviCRM tables.
  3. Make sure you are logged into your Drupal site as the administrator.
  4. Visit http://example.org/civicrm/admin/setting/uf?reset=1
  5. You should see a page with output that begins with: $databases['default']['default']['prefix']= array(

    Screenshot showing the "Drupal Integration" page, with output of settings to be placed into settings.php

  6. Copy this setting output, including the trailing );

  7. Open the file /sites/default/settings.php for editing from the root directory of the site, typically public_html on most servers.


    This assumes you have a single site installation. The location of the settings file might be different depending on whether or not you have multiple sites

  8. Go to the bottom of the file and paste in your previously-copied settings output here. If the settings.php file already includes an earlier version of the output please remove the earlier version before pasting the new output.

    Screenshot demonstrating the output of database settings

  9. You may need to indicate the default prefix. If you see an error like the one below:

    PDOException: SQLSTATE[42S02]: Base table or view not found: 1146 Table 'kckruppc_every.semaphore' doesn't exist: SELECT ...

    You need to include an additional line, 'default' => '<drupaltableprefix>', in your settings.php just after $database ['default']['default']['prefix']= array(. You can find more information on this error in this forum post.

    Screenshot demonstrating where to add a table prefix in your settings

  10. Save the file settings.php. You might want to clear your site cache at this point.

  11. You should now be able to create Drupal Views based on CiviCRM data.

!!! note If you add a new set of custom fields to CiviCRM you will need to re-do these steps again. So any new fields in the field set can be accessed by Drupal Views.

Drupal 6

NOTE: For Drupal 6 the variable name in the settings.php file is different. Rather than $databases['default']['default']['prefix']= array(, for Drupal 6 the relevant array is $db_prefix, so the beginning lines of the addition to settings.php will look something like this:

$db_prefix = array (
 'default' => 'dru_',
 'civicrm_acl' => '`civicrmdb`.',
 'civicrm_acl_cache' => '`civicrmdb`.',
 'civicrm_acl_contact_cache' => '`civicrmdb`.',
 'civicrm_acl_entity_role' => '`civicrmdb`.',
 'civicrm_action_log' => '`civicrmdb`.',
 'civicrm_action_mapping' => '`civicrmdb`.',
 'civicrm_action_schedule' => '`civicrmdb`.',
 'civicrm_activity' => '`civicrmdb`.',
 'civicrm_activity_assignment' => '`civicrmdb`.',
 'civicrm_activity_target' => '`civicrmdb`.',


That example is for a Drupal set that uses table prefix dru_ and for which CiviCRM is set up to use a separate table named civicrmdb. CiviCRM also uses a table prefix but that is automatically added–do not add it again here.

Also–if you use a table prefix in Drupal 6 you probably already have a $db_prefix="dru_"; or similar statement in your settings.php. So you will need to remove any existing declaration of $db_prefix and replace it with one similar to above.