Details
-
Type:
Bug
-
Status: Reopened
-
Priority:
Major
-
Resolution: Unresolved
-
Affects Version/s: 4.7, 4.7.4
-
Fix Version/s: Unscheduled
-
Component/s: Drupal Integration Modules
-
Labels:
-
Versioning Impact:Patch (backwards-compatible bug fixes)
-
Documentation Required?:None
-
Funding Source:Needs Funding
Description
I think this regression was introduced by CRM-17468
PR: https://github.com/civicrm/civicrm-drupal/pull/323
We used to be able to use Address ID / Phone ID / Email ID as fields in CiviCRM's Views integration.
These fields no longer appear in the list, and any instances of it from before upgrading to 4.7 display 'Broken/missing handler'.
It doesn't seem that there was any upgrade notice/code to change how this works if a change in how we build Views was required.
It seems there are two conflicting ways to display contact's addresses using views now. Using the fields directly, or using the relationship. This seems like bad practice and we should be enforcing accessing these entities via the relationship if this is the new approach - we should 'deprecate' the old fields (but not delete them).
Even using the new relationships the address/phone/email IDs do not appear as a 'field' that can be added.
Attachments
Activity
John K. do you have any ideas about how this ought to be fixed?
Please check my attached above I didn't encountered any issue against desired fields in view against latest civicrm 4.7.10. Am closing the issue, feel free to reopen the issue if you are able to replicate the issue. Thanks!
Still a problem in master I think Monish Deb
Steps to recreate:
- Add a new view: CiviCRM Contacts
- Notice that you cannot add CiviCRM Email: Email Address as a field, but not the Email address ID
- Add a relationship to the CiviCRM Email Address table
- Notice that you still cannot add the Email address entity ID as a field.
The same goes for addresses, phones...
It's the IDs of those entities we can't access, the Contact ID itself is accessible OK.
I think this:
https://issues.civicrm.org/jira/browse/CRM-18147
Is similar to the previous issue.