Answers.Body: <p>Have you tried clearing all Drupal caches then running update.php for Drupal? This fixes views for me</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-04-16T17:11:14.167Z
Answers.Text: Thank you... that seems to fix the issue I had with the last update. However I still have the issue with the custom fields.
  
  SQLSTATE[42S22]: Column not found: 1054 Unknown column 'civicrm_contact.custom_7' in 'where clause'
  
  I still have this issue and the column indeed does not exist.
Answers.UserDisplayName: Ronald
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-04-17T21:11:04.300Z
Answers.Text: if you are using civicrm entity module you often get Fields showing in Views - those are the ones that have 'no help' or somesuch message in your Field selector - avoid those ones.
Answers.UserDisplayName: petednz - fuzion
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-04-19T06:41:41.887Z
Answers.Text: The Entity module seems to indeed be the problem. I disabled the entity module and the fields show up fine now.
Answers.UserDisplayName: Ronald
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-04-16T16:18:00.607Z
Answers.LastActivityDate: 2016-04-16T16:18:00.607Z
Answers.UserDisplayName: Robin Fenwick
Answers.Body: <p>In my case I needed civicrm_entity_views_extras and therefore both entity and  civicrm_entity, so disabling is not an option. My civicrm views break as soon as I migrate from production to stage. Clearing all drupal cache (which includes views) is not helping me. The only thing that seems to help is</p>
  
  <ul>
  <li>Access the failing view</li>
  <li>Specifically clear the views cache (drush cc views)</li>
  </ul>
  
  <p>Apparently it should fail once and only then after cache cleared again, the cache is finally build properly. I will try now to deactivate views cache before migrating to see if that helps. </p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2018-02-08T13:48:17.220Z
Answers.Text: The best solution imho is to simple disable views data cache in advanced views settings. I did not notice any speed gain in my situation and reports are not accessed by all and not daily.
Answers.UserDisplayName: ñull
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2018-02-08T13:30:13.423Z
Answers.LastActivityDate: 2018-02-08T13:30:13.423Z
Answers.UserDisplayName: ñull
Body: <p>Since the last two updates I am having severe issues with the views integration with Drupal. The views module hasn't changed, but it doesn't seem to work after the 4.74 and 4.76 updates. </p>
  
  <p>When upgrading to 4.74 I lost all the custom fields in the integration and now with the 4.76 I lost even more fields like event names, dates and contact fields. </p>
  
  <p>Does anyone else have this issue and knows how to fix it?</p>
  
Tags: <drupal><drupal-views>
Title: Views integration broken
ThreadText: # Views integration broken
  
  (Asked by: username_0 on 2016-04-16)
  
  Since the last two updates I am having severe issues with the views integration with Drupal. The views module hasn't changed, but it doesn't seem to work after the 4.74 and 4.76 updates.
  
  When upgrading to 4.74 I lost all the custom fields in the integration and now with the 4.76 I lost even more fields like event names, dates and contact fields.
  
  Does anyone else have this issue and knows how to fix it?
  
  **Tags:** drupal, drupal-views
  
  
  ---
  
  ## 2 answers
  
  ### Answer by username_1 on 2016-04-16. Score: 1 | Accepted answer
  
  Have you tried clearing all Drupal caches then running update.php for Drupal? This fixes views for me
  
  > **Comments:**
  > **username_0**: Thank you... that seems to fix the issue I had with the last update. However I still have the issue with the custom fields.  SQLSTATE[42S22]: Column not found: 1054 Unknown column 'civicrm_contact.custom_7' in 'where clause'  I still have this issue and the column indeed does not exist.  
  > **username_2**: if you are using civicrm entity module you often get Fields showing in Views - those are the ones that have 'no help' or somesuch message in your Field selector - avoid those ones.  
  > **username_0**: The Entity module seems to indeed be the problem. I disabled the entity module and the fields show up fine now.  
  
  ---
  
  ### Answer by username_3 on 2018-02-08. Score: 1
  
  In my case I needed civicrm\_entity\_views\_extras and therefore both entity and civicrm\_entity, so disabling is not an option. My civicrm views break as soon as I migrate from production to stage. Clearing all drupal cache (which includes views) is not helping me. The only thing that seems to help is
  
  * Access the failing view
  * Specifically clear the views cache (drush cc views)
  
  Apparently it should fail once and only then after cache cleared again, the cache is finally build properly. I will try now to deactivate views cache before migrating to see if that helps.
  
  > **Comments:**
  > **username_3**: The best solution imho is to simple disable views data cache in advanced views settings. I did not notice any speed gain in my situation and reports are not accessed by all and not daily.  
  
  ---
  
  