Answers.Body: <p>You will need to add the field manually to:</p>
  
  <p>drupal/modules/views/components/civicrm.core.inc</p>
  
  <p>and then submit a PR to civicrm-drupal repository, so the fix gets merged into the main code base.</p>
  
  <p>In D8, the situation is a lot better, as torrance has automated the process and the fields and their definition get picked up automatically. So a lot cleaner and easier on everyone.</p>
  
  <p>But for now, the above is your best bet and will help views intergration for D7 and prior</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-06-17T13:05:28.983Z
Answers.LastActivityDate: 2015-06-17T13:05:28.983Z
Answers.UserDisplayName: Donald Lobo
Answers.Body: <p>There are three ways to do this.  Lobo detailed one of them, and alluded to work done for D8 to automate this - but similar work has been done for D7 as well.</p>
  
  <p>The other two options each involve installing a module:  Either <a href="https://www.drupal.org/project/civicrm_entity" rel="nofollow">civicrm_entity</a> 2.0, or <a href="https://www.drupal.org/sandbox/markusa/2474103" rel="nofollow">Views CiviCRM Expose Tables</a>.  Views Expose Tables can expose every field in every CiviCRM table.  CiviCRM Entity works with fewer tables, but a) it's the ones you probably want, and b) it has applicability beyond Views - e.g. you can use it for Rules integration.</p>
  
  <p>There was an excellent presentation by Mark Hanna from <a href="https://skvare.com/" rel="nofollow">Sqvare</a> at CiviCon Denver 2015: <a href="https://denver2015.civicrm.org/sessions/civicrmdrupal-integration-showcase" rel="nofollow">https://denver2015.civicrm.org/sessions/civicrmdrupal-integration-showcase</a>.  The video's not up yet, but the PDF of the slides is, and it's well worth reading, not just for Views integration.</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-06-17T16:22:02.360Z
Answers.LastActivityDate: 2015-06-17T16:22:02.360Z
Answers.UserDisplayName: Jon G - Megaphone Tech
Body: <p>For example, the email_greeting_display field of the civicrm_contact table is not available as a field in Views.  How do I add that to a View?</p>
  
  <p>See also <a href="https://civicrm.stackexchange.com/q/3086/225">How to include a token in a view?</a></p>
  
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2015-06-14T12:43:27.520Z
Comments.Text: In  my opinion, this is one of those ares where there really needs to be some additional documentation and integration built into CiviCRM.
  
  This would increase functionality and lower the learning curve  dramatically
Comments.UserDisplayName: pmoz
Tags: <drupal-views>
Title: How do I add a currently unsupported field to Views?
ThreadText: # How do I add a currently unsupported field to Views?
  
  (Asked by: username_0 on 2015-06-09)
  
  For example, the email\_greeting\_display field of the civicrm\_contact table is not available as a field in Views. How do I add that to a View?
  
  See also [How to include a token in a view?](https://civicrm.stackexchange.com/q/3086/225)
  
  **Tags:** drupal-views
  
  > **Comments:**
  > **username_1**: In  my opinion, this is one of those ares where there really needs to be some additional documentation and integration built into CiviCRM.  This would increase functionality and lower the learning curve  dramatically  
  
  ---
  
  ## 2 answers
  
  ### Answer by username_2 on 2015-06-17. Score: 4
  
  You will need to add the field manually to:
  
  drupal/modules/views/components/civicrm.core.inc
  
  and then submit a PR to civicrm-drupal repository, so the fix gets merged into the main code base.
  
  In D8, the situation is a lot better, as torrance has automated the process and the fields and their definition get picked up automatically. So a lot cleaner and easier on everyone.
  
  But for now, the above is your best bet and will help views intergration for D7 and prior
  
  
  ---
  
  ### Answer by username_3 on 2015-06-17. Score: 4
  
  There are three ways to do this. username_2 detailed one of them, and alluded to work done for D8 to automate this - but similar work has been done for D7 as well.
  
  The other two options each involve installing a module: Either [civicrm\_entity](https://www.drupal.org/project/civicrm_entity) 2.0, or [Views CiviCRM Expose Tables](https://www.drupal.org/sandbox/markusa/2474103). Views Expose Tables can expose every field in every CiviCRM table. CiviCRM Entity works with fewer tables, but a) it's the ones you probably want, and b) it has applicability beyond Views - e.g. you can use it for Rules integration.
  
  There was an excellent presentation by Mark Hanna from [Sqvare](https://skvare.com/) at CiviCon Denver 2015: <https://denver2015.civicrm.org/sessions/civicrmdrupal-integration-showcase>. The video's not up yet, but the PDF of the slides is, and it's well worth reading, not just for Views integration.
  
  
  ---
  
  