Answers.Body: <p>I think this is a symptom of a structural issue: you have Drupal fields on a contact. Perhaps they're best brought into Civi?</p>
  
  <p>The quickest option is to give those Drupal fields default values for when they haven't been filled in.</p>
  
  <p>An alternative is to create some kind of custom extension or custom module that prevents this issue for you.</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-03-23T17:44:42.123Z
Answers.Text: Hey John, the question was updated for clarity - We're using a CiviCRM Profile with "Drupal User Registration" enabled which shows the profile on the registration form. But we also have a custom field on the Drupal user page too (admin/config/people/accounts/fields) that allows Organic Group selection. Thanks.
Answers.UserDisplayName: Alex Katayama
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-03-23T18:58:26.620Z
Answers.Text: John's suggestion about setting a default value would be one way out of this.
Answers.UserDisplayName: petednz - fuzion
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-03-22T21:40:52.270Z
Answers.LastActivityDate: 2016-03-22T21:40:52.270Z
Answers.UserDisplayName: JohnFF
Body: <p>From the back office admin, creating a user is impossible if there are Drupal fields attached that are required. The workaround has been to temporarily unmark the fields as required, but this is tedious. Is there some modification we can make for it to ignore required Drupal fields when we use this function?</p>
  
  <p>Editing for clarity:</p>
  
  <ol>
  <li><p>Users register on the Drupal front end - there's a CiviCRM Membership Profile form that asks for additional information.</p></li>
  <li><p>On top of the Profile (which updates the CiviCRM record), we have a Drupal User field (image below) that allows the User to join an Organic Group at registration (required field).</p></li>
  </ol>
  
  <p><a href="https://i.sstatic.net/qdEyT.png" rel="nofollow noreferrer"><img src="https://i.sstatic.net/qdEyT.png" alt="enter image description here"></a></p>
  
  <ol start="3">
  <li>Because this field is required, we cannot use the "Create User Record" function on the CiviCRM Contact record because of the validation error on the required field.</li>
  </ol>
  
  <p><a href="https://i.sstatic.net/btSen.jpg" rel="nofollow noreferrer"><img src="https://i.sstatic.net/btSen.jpg" alt="enter image description here"></a></p>
  
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2016-03-23T00:03:57.950Z
Comments.Text: Not sure i follow. Alex you may need to explain this more. Are you using Drupal Profile (which adds Drupal fields on the Drupal User), or do you mean there are required civicrm fields showing in the Profile that is used for drupal user? or something else
Comments.UserDisplayName: petednz - fuzion
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2016-03-23T17:42:12.907Z
Comments.Text: Hi Pete - I've edited the original question for clarity. We're using a CiviCRM Profile with "Drupal User Registration" enabled which shows the profile on the registration form. But we also have a custom field on the Drupal user page too (admin/config/people/accounts/fields) that allows Organic Group selection.
Comments.UserDisplayName: Alex Katayama
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2016-03-23T18:57:04.917Z
Comments.Text: So in a sense, civi 'create user record' is doing the 'right' thing in terms of the drupal user creation requiring the field that you are requiring. not sure this will be an easy civi fix - if it is a civi issue at all. perhaps there are ways around 'requiring' the OG field such as using a sync tool that adds contacts to the OG based on some civi characteristic? if so i would fork that off as a separate question. and i will turn this in to an answer
Comments.UserDisplayName: petednz - fuzion
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2016-03-23T18:59:55.607Z
Comments.Text: do the back office Admin know which Chapter they should be adding people to when they create these drupal users?
Comments.UserDisplayName: petednz - fuzion
Tags: <drupal><civimember><user-account>
Title: "Create User Record" - possible to ignore required Drupal User custom fields?
ThreadText: # "Create User Record" - possible to ignore required Drupal User custom fields?
  
  (Asked by: username_0 on 2016-03-22)
  
  From the back office admin, creating a user is impossible if there are Drupal fields attached that are required. The workaround has been to temporarily unmark the fields as required, but this is tedious. Is there some modification we can make for it to ignore required Drupal fields when we use this function?
  
  Editing for clarity:
  
  1. Users register on the Drupal front end - there's a CiviCRM Membership Profile form that asks for additional information.
  2. On top of the Profile (which updates the CiviCRM record), we have a Drupal User field (image below) that allows the User to join an Organic Group at registration (required field).
  
  [![enter image description here](https://i.sstatic.net/qdEyT.png)](https://i.sstatic.net/qdEyT.png)
  
  3. Because this field is required, we cannot use the "Create User Record" function on the CiviCRM Contact record because of the validation error on the required field.
  
  [![enter image description here](https://i.sstatic.net/btSen.jpg)](https://i.sstatic.net/btSen.jpg)
  
  **Tags:** drupal, civimember, user-account
  
  > **Comments:**
  > **username_1**: Not sure i follow. Alex you may need to explain this more. Are you using Drupal Profile (which adds Drupal fields on the Drupal User), or do you mean there are required civicrm fields showing in the Profile that is used for drupal user? or something else  
  > **username_0**: Hi Pete - I've edited the original question for clarity. We're using a CiviCRM Profile with "Drupal User Registration" enabled which shows the profile on the registration form. But we also have a custom field on the Drupal user page too (admin/config/people/accounts/fields) that allows Organic Group selection.  
  > **username_1**: So in a sense, civi 'create user record' is doing the 'right' thing in terms of the drupal user creation requiring the field that you are requiring. not sure this will be an easy civi fix - if it is a civi issue at all. perhaps there are ways around 'requiring' the OG field such as using a sync tool that adds contacts to the OG based on some civi characteristic? if so i would fork that off as a separate question. and i will turn this in to an answer  
  > **username_1**: do the back office Admin know which Chapter they should be adding people to when they create these drupal users?  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_2 on 2016-03-22. Score: 1
  
  I think this is a symptom of a structural issue: you have Drupal fields on a contact. Perhaps they're best brought into Civi?
  
  The quickest option is to give those Drupal fields default values for when they haven't been filled in.
  
  An alternative is to create some kind of custom extension or custom module that prevents this issue for you.
  
  > **Comments:**
  > **username_0**: Hey John, the question was updated for clarity - We're using a CiviCRM Profile with "Drupal User Registration" enabled which shows the profile on the registration form. But we also have a custom field on the Drupal user page too (admin/config/people/accounts/fields) that allows Organic Group selection. Thanks.  
  > **username_1**: John's suggestion about setting a default value would be one way out of this.  
  
  ---
  
  