Answers.Body: <p>Just ran into the issue when upgrading from 4.7.13 to 4.7.16. Spent way too much time trying to figure it out and far too many views data cache clears/drush cc all. </p>
  
  <p>In case anyone runs across this having the same problem, this is a direct link to the revert patch mentioned above: <a href="https://github.com/civicrm/civicrm-drupal/pull/417/commits/b40430781786aa2102a2fa0aa289c1f55a64911d" rel="nofollow noreferrer">CRM-19545: Revert CRM-18776 to get back missing custom fields </a></p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2017-03-06T02:39:00.850Z
Answers.LastActivityDate: 2017-03-06T02:39:00.850Z
Answers.UserDisplayName: eyeonall
Body: <p>I have a report in views that pulls data from custom fields on a relationship between two contacts.</p>
  
  <p>Since an upgrade to 4.7.15 It is no longer displaying that data and on opening the view I see that the fields have the notice "missing handler"</p>
  
  <p>I've cleared caches and ensured that the Drupal database is fully updated and so on. </p>
  
  <p>Could this may be another symptom of: CRM-19545. PR-417</p>
  
  <p>Can anyone shed light or suggests steps to resolve?</p>
  
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2017-01-29T02:05:38.160Z
Comments.Text: What did you upgrade from? The way we handle Relationships in Views was changed quite a long time ago. But without knowing your previous version it may not be relevant
Comments.UserDisplayName: petednz - fuzion
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2017-01-29T02:07:02.710Z
Comments.Text: also i see that jira issues says Fixed for 4.7.17 so upgrading to that seems to make sense if only to rule out that as being an issue.
Comments.UserDisplayName: petednz - fuzion
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2017-01-29T09:15:32.497Z
Comments.Text: @petednz - fuzion - Thanks for your comments  - Upgraded from 4.7.10  (for a charity I used to work with that has not had any maintenance for some time) - I have also seen that the fix has been committed to the 4.7.17 release but presumably 17 will be released after 16 which has not yet been released... I have been unable to find the patch to apply as an interim measure.
Comments.UserDisplayName: theTechnaddict
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2017-01-29T09:24:09.390Z
Comments.Text: I've manually applied the changes given in the commit - all working.
Comments.UserDisplayName: theTechnaddict
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2018-07-16T20:39:07.743Z
Comments.Text: I am having the same issue, i upgraded from CiviCRM 4.7.27 to 5.3.0. Its failing for not only custom fields but CiviCRM events fields also like title, start_date, etc.
Comments.UserDisplayName: Hassan Farooq
Tags: <drupal-views>
Title: Views integration - Missing handler for custom fields on relationships broken since upgrade to 4.7.15
ThreadText: # Views integration - Missing handler for custom fields on relationships broken since upgrade to 4.7.15
  
  (Asked by: username_0 on 2017-01-28)
  
  I have a report in views that pulls data from custom fields on a relationship between two contacts.
  
  Since an upgrade to 4.7.15 It is no longer displaying that data and on opening the view I see that the fields have the notice "missing handler"
  
  I've cleared caches and ensured that the Drupal database is fully updated and so on.
  
  Could this may be another symptom of: CRM-19545. PR-417
  
  Can anyone shed light or suggests steps to resolve?
  
  **Tags:** drupal-views
  
  > **Comments:**
  > **username_1**: What did you upgrade from? The way we handle Relationships in Views was changed quite a long time ago. But without knowing your previous version it may not be relevant  
  > **username_1**: also i see that jira issues says Fixed for 4.7.17 so upgrading to that seems to make sense if only to rule out that as being an issue.  
  > **username_0**: @username_1 - Thanks for your comments  - Upgraded from 4.7.10  (for a charity I used to work with that has not had any maintenance for some time) - I have also seen that the fix has been committed to the 4.7.17 release but presumably 17 will be released after 16 which has not yet been released... I have been unable to find the patch to apply as an interim measure.  
  > **username_0**: I've manually applied the changes given in the commit - all working.  
  > **username_2**: I am having the same issue, i upgraded from CiviCRM 4.7.27 to 5.3.0. Its failing for not only custom fields but CiviCRM events fields also like title, start_date, etc.  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_3 on 2017-03-06. Score: 2
  
  Just ran into the issue when upgrading from 4.7.13 to 4.7.16. Spent way too much time trying to figure it out and far too many views data cache clears/drush cc all.
  
  In case anyone runs across this having the same problem, this is a direct link to the revert patch mentioned above: [CRM-19545: Revert CRM-18776 to get back missing custom fields](https://github.com/civicrm/civicrm-drupal/pull/417/commits/b40430781786aa2102a2fa0aa289c1f55a64911d)
  
  
  ---
  
  