CiviCRM Community Forums (archive)

Drupal Views 2 has a glossary view attached to the argument 'node: title'.  Is there any way to create a similar view to contact: last name?  The glossary view groups node titles by letter, it would be helpful if a glossary of last names was available.  Has anyone done this?

The views file which controls this in Views is: views_handler_argument_string.inc, and modifies fields that are text strings.  Any way to hook into this?

In the custom module:

// This function is called after a db write on some objects
// Should be able to get Last Name in English here
function modulename_civicrm_post( $op, $objectName, $objectId, &$objectRef) {
        if ( $op != 'create' && $op != 'edit') {
                return;
        }
 
        if ( $objectName != 'Individual') {
                // we work only with Individuals here
                return;
        }
       
        // Cool! The individual name is already in the $objectRef, [0...30], last_name
       
        if ( isset ($objectRef->last_name)) {
            $lastname_en = $objectRef->last_name;
            $letter_en = $lastname_en[0];
       
            $groupID = 1; // constituent_information
            $needs_update = false;
            $tableName = CRM_Core_DAO::getFieldValue('CRM_Core_DAO_CustomGroup',
                                                                $groupID,
                                                                'table_name');
                                                               
            $sql = "SELECT last_name_letter__en__71 from $tableName WHERE entity_id = $objectId";
            $dao = CRM_Core_DAO::executeQuery( $sql, CRM_Core_DAO::$_nullArray );
                                                               
            if (! $dao->fetch()) {
                $needs_update = true;
            }
           
            if (! $dao->last_name_letter__en__71) {
                //value may also be empty... Copied this from example, will test how it works
                $needs_update = true;
            }
            else {
                if ( $dao->last_name_letter__en__71 != $letter_en) {
                    $needs_update = true;
                }
            }
           
           
            if ($needs_update) {
                $sql = "UPDATE $tableName SET last_name_letter__en__71 = \"$letter_en\" WHERE entity_id = $objectId";
                CRM_Core_DAO::executeQuery( $sql, CRM_Core_DAO::$_nullArray);
            }               
        }
}

Comments and suggestions are welcomed.

Hello, Mariagwyn.

1. I created a field named "Last Name Letter (En)", view only, and checked the internal name of the field somewhere in tables of CiviCRM (please read documentation on where to do that, it should be in a table corresponding to your Custom Fields group). The internal name occured to be last_name_letter__en__71.

2. Yes, it's a custom module where I put all custom written hooks.

3. CRM_Core_DAO_CustomGroup is a name of some internal CiviCRM constant, I think. You should not rename it. I found this particular line in some example in the Documentations area (don't remeber which one).

4. Debug on test server (or local machine) first. It's easy to put all site to a WSOD by a simple misprint in the custom module

Regards,
Danila