CiviCRM Community Forums (archive)

When I create a very simple view based on CiviCRM Contacts and show only the Contact ID and contact_type the contact type looks to be blank like this:

Contact ID: 1
Contact Type:
Contact ID: 11
Contact Type:

I can verify that on both my live and demo sites using civi 4.2.6  I can't test it on demo since I can't create views there.

I hunted around and in civicrm.views.inc on line 170+ I see

 function civicrm_views_add_fields(&$fields, &$data, $tableName, &$skipFields = NULL) {
   foreach ($fields as $name => $value) {
    // Only add fields not in $data or $skipFields and has a ['title']
    if (isset($value['custom_field_id']) ||
      CRM_Utils_Array::value($name, $skipFields) ||
      CRM_Utils_Array::value($name, $data) ||
      !isset($value['title']) ||
      (isset($value['where']) &&
        substr($value['where'], 0, strlen($tableName) + 1) != "{$tableName}."
      )
    ) {
      continue;
    }

If I remove CRM_Utils_Array::value($name, $data) || from that condition then civicrm_type begins to display the contact_type as I would expect like this:

Contact ID: 1
Contact Type: Individual
Contact ID: 11
Contact Type: Individual

I'm sure that's not the right way to fix it, it's just a hint for someone else who might know how to do it properly.  I know for sure this isn't the right way to fix it because when I take that out it changes the way the contact_type filters work.  When "CRM_Utils_Array::value($name, $data) ||" is left in, when you filter by contact_type you are presented with the option to tick check boxes for the types you want, but after taking that line out, when you filter it looks like a free text field.   And worse, it breaks any views set up to filter on contact type the "normal" way with "CRM_Utils_Array::value($name, $data) ||" left in.

I know only enough about this to be dangerous.  Is there someone else with a better handle on views integration who could decide on a good fix for this, or give me a push in the right direction?

     

seems to work fine on 4.4.3, see screen capture below. You may consider upgrading