Answers.Body: <p>See <a href="https://issues.civicrm.org/jira/browse/CRM-19545" rel="nofollow noreferrer">CRM-19545</a>  There was a a regression introduced in 4.7.14 and fixed in 4.7.17  If you want the fix sooner see <a href="https://github.com/civicrm/civicrm-drupal/pull/417/files" rel="nofollow noreferrer">https://github.com/civicrm/civicrm-drupal/pull/417/files</a></p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2017-02-03T09:20:54.590Z
Answers.Text: This is the correct answer. It was bugged.
Answers.UserDisplayName: JohnFF
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2017-09-02T09:02:26.553Z
Answers.Text: How can I apply this bug fix as a patch?
Answers.UserDisplayName: Christia
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2017-09-04T08:27:08.017Z
Answers.Text: @Christia the preferred option now would be to upgrade to the latest (4.7.23) which includes this fix and numerous others.  Is there a reason why you can't upgrade?
Answers.UserDisplayName: Aidan
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2017-09-05T22:22:17.593Z
Answers.Text: Yes of course. I have to wait until launch time so that I can bring over the data from a legacy database in the version it's in (4.7.15). I did end up doing a test upgrade and it didn't end up solving the problem for me.
Answers.UserDisplayName: Christia
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2017-09-06T07:53:57.150Z
Answers.Text: In that case, see https://github.com/civicrm/civicrm-drupal/pull/417/files  Edit modules/views/components/civicrm.core.inc on your system, find the lines that are highlighted on the left starting at line 2942 and change them to match those highlighted on the right.  Note that the +- symbols in the first column show what has been changed and do not appear in the source file.   But ... if you have already tried a test upgrade without success then you may have a different problem.
Answers.UserDisplayName: Aidan
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2017-02-02T11:58:53.990Z
Answers.LastActivityDate: 2017-02-02T11:58:53.990Z
Answers.UserDisplayName: Aidan
Body: <p>I'm struggling for custom fields to appear in my Drupal views. They just aren't. I've populated my CiviCRM tables into the Drupal settings table, but they just aren't appearing.</p>
  
  <p>Standard fields appear fine. It's just custom ones.</p>
  
  <p>Please can anyone tell me a) if they've experienced the same thing lately? and b) where I should start debugging?</p>
  
  <p>Should I be using CiviCRM Entity for this? Never needed to before.</p>
  
  <p>Thanks,</p>
  
  <p>John</p>
  
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2017-02-01T20:26:19.357Z
Comments.Text: shouldn't need civicrm entity - are your tables in single db or one for drupal and one for civi - in which case you need to add the prefix 'stuff' in settings.php
Comments.UserDisplayName: petednz - fuzion
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2017-02-01T20:34:22.030Z
Comments.Text: Thanks for the response. I've done the prefix stuff in settings.php but the custom fields - only the custom ones - aren't appearing in the list. Any suggestions for how I can debug this?
Comments.UserDisplayName: JohnFF
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2017-02-02T03:43:19.253Z
Comments.Text: Just to be clear, you put the info into settings.php after creating the custom data fields in Civi, correct? I once added a custom field a few months after installation and couldn't figure out for the life of me why Views wasn't finding it... I hadn't redone the settings file.
Comments.UserDisplayName: Allen Hutchison
Tags: <drupal-views>
Title: Custom Data in Drupal Views
ThreadText: # Custom Data in Drupal Views
  
  (Asked by: username_0 on 2017-02-01)
  
  I'm struggling for custom fields to appear in my Drupal views. They just aren't. I've populated my CiviCRM tables into the Drupal settings table, but they just aren't appearing.
  
  Standard fields appear fine. It's just custom ones.
  
  Please can anyone tell me a) if they've experienced the same thing lately? and b) where I should start debugging?
  
  Should I be using CiviCRM Entity for this? Never needed to before.
  
  Thanks,
  
  John
  
  **Tags:** drupal-views
  
  > **Comments:**
  > **username_1**: shouldn't need civicrm entity - are your tables in single db or one for drupal and one for civi - in which case you need to add the prefix 'stuff' in settings.php  
  > **username_0**: Thanks for the response. I've done the prefix stuff in settings.php but the custom fields - only the custom ones - aren't appearing in the list. Any suggestions for how I can debug this?  
  > **username_2**: Just to be clear, you put the info into settings.php after creating the custom data fields in Civi, correct? I once added a custom field a few months after installation and couldn't figure out for the life of me why Views wasn't finding it... I hadn't redone the settings file.  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_3 on 2017-02-02. Score: 2 | Accepted answer
  
  See [CRM-19545](https://issues.civicrm.org/jira/browse/CRM-19545) There was a a regression introduced in 4.7.14 and fixed in 4.7.17 If you want the fix sooner see <https://github.com/civicrm/civicrm-drupal/pull/417/files>
  
  > **Comments:**
  > **username_0**: This is the correct answer. It was bugged.  
  > **username_4**: How can I apply this bug fix as a patch?  
  > **username_3**: @username_4 the preferred option now would be to upgrade to the latest (4.7.23) which includes this fix and numerous others.  Is there a reason why you can't upgrade?  
  > **username_4**: Yes of course. I have to wait until launch time so that I can bring over the data from a legacy database in the version it's in (4.7.15). I did end up doing a test upgrade and it didn't end up solving the problem for me.  
  > **username_3**: In that case, see https://github.com/civicrm/civicrm-drupal/pull/417/files  Edit modules/views/components/civicrm.core.inc on your system, find the lines that are highlighted on the left starting at line 2942 and change them to match those highlighted on the right.  Note that the +- symbols in the first column show what has been changed and do not appear in the source file.   But ... if you have already tried a test upgrade without success then you may have a different problem.  
  
  ---
  
  