Details
-
Type: Bug
-
Status: Done/Fixed
-
Priority: Major
-
Resolution: Fixed/Completed
-
Affects Version/s: 4.7.14
-
Fix Version/s: 4.7.15
-
Component/s: Drupal Integration Modules
-
Labels:
-
Versioning Impact:Patch (backwards-compatible bug fixes)
-
Documentation Required?:None
-
Funding Source:Contributed Code
-
Verified?:No
Description
This regression was introduced in CRM-19274
Prior to 4.7.14 it was possible to list several phone numbers for a contact in Drupal Views using four fields, such as:
CiviCRM Phone Details: Phone (Home)
CiviCRM Phone Details: Phone (Home mobile)
CiviCRM Phone Details: Phone (Work)
CiviCRM Phone Details: Phone (Work mobile)
Each field would be set up to only show a certain combination of Location Type and Phone Type, eg:
Since upgrading the SQL has changed and this only displays one phone number, multiple times. The phone table is not being joined multiple times. So the output is:
Home: 0333 333
Home mobile: 0333 333
...
It is now required to add a relationship to the 'Phone detail' and then add this relationship to each phone field, eg:
(Related Phone) CiviCRM Phone Details: Phone (Home)
(Related Phone) CiviCRM Phone Details: Phone (Home mobile)
(Related Phone) CiviCRM Phone Details: Phone (Work)
(Related Phone) CiviCRM Phone Details: Phone (Work mobile)
This displays the different phone numbers correctly:
Home: 01111 111 111
Home mobile: 02222 222
...
—
If we are now required to create a relationship in order to use the Phone detail: phone field correctly, then it should not be possible to add these fields to the view without the relationship being defined.
I consider this a regression because it has altered functionality, and necessitated a change to any Drupal Views that list phone numbers from CiviCRM.
Attachments
Issue Links
- supplements
-
CRM-19274 Access Instant Messaging in Drupal Views
- Done/Fixed
- links to