CiviCRM Community Forums (archive)

Can anyone shed a bit of light for me. Having my first look in to Views (using 3 since the common word is 2 will never made it to beta and is being superceded by 3 which is at alpha4 - if you cared)

Just curious if I am missing the v obvious. Starting with "items of type CiviCRM Contacts" and using 'relationships' I get the option for A-B which spits me out a lovely list, and when I filter by = Employee of I get just those contacts with 'employee of'.

But in "CiviCRM Relationships" there is "Relationship Type A-to-B. The Type of Relationship, i.e. Employee of, Household Head for..." but no equivalent B-to-A. Is that intentional, only thing possible, an oversight?

cheers

How can anyone understand what I am talking about when I write that 'alpha' stuff about Views when of course that reference was to Panels. 

Ok, will probably have to take a look at B - A, not sure which of us will pop on to IRC for some pointers.

Views export will not help much in this situation, as Relationship custom fields table names depend on each setup... So just a description of what you whant to achieve will be enough.

Regards,
Danila

Hello, Peterd.

Try the following:

Go to Views administration page, add new view.
In View type, select "CiviCRM Relationships"
Get, for example, 'Relationship description' into fields
In 'relationships' tab of views interface add both Contact ID A and Contact ID B

Now go again to fields to add more information. For example, select 'CiviCRM Contact: Contact ID' and 'CiviCRM Contact: Display name'.

After this when you press 'add', there will be a drop-down allowing you to select

Relationship:
      - Contact ID A
      - Contact ID B

This way you can specify contact from which side of relationship should provide the data.

Regards,
Danila

ho ho ho - that is so cool 

how can this all be so easy!

big thanks

There are two ways to do this.

Proper way is to write something similar to civicrm_handler_field_relationship_type.inc or civicrm_handler_field_relationshipType.inc (or maybe both, don't remember currently why we need both of them) and to get 'name_b_a' from CRM_Core_PseudoConstant::relationshipType( );. Maybe it's possible to change those two files without creating new ones. After this a proper description of how to handle this info is to be added to civicrm.views.inc.

Faster way (in terms of implementing, probably. It will definitely cause longer SQL) is to add an additional 'join' to civicrm_relationship_type table (not sure of exact name) inside civicrm.views.inc here:

//TABLE JOINS FOR CIVICRM RELATIONSHIPS GO HERE!
 
    $data['civicrm_relationship']['table']['join'] = array(
                                                           // Directly links to contact table - link A
                                                           'civicrm_contact' => array(
                                                                                      'left_field' => 'id',
                                                                                      'field' => 'contact_id_a',
                                                                                      ),
                                                           // Directly links to contact table - link B also.
                                                           //    'civicrm_contact' => array(
                                                           //   'left_field' => 'id',
                                                           //   'field' => 'contact_id_b',
                                                           //   ),
                                                           );
 
and then describe additional fields later. You will need to use Views feature 'relationship' to link to CiviCRM Relationship type table and then get the data into fields specifying that the source of the data is Relationship type table.

Please submit your patch if you do this.

Regards,
Danila