Answers.Body: <p>I found that if a Select field has <code>options_per_line</code> set in <code>civicrm_custom_field</code>, then it fails to render, as described. A workaround is to unset Options Per Line in the UI before changing the field type, or set <code>options_per_line</code> to NULL in the database. The Select field then renders as it should.</p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2021-06-25T11:32:18.480Z
Answers.LastActivityDate: 2021-06-25T11:32:18.480Z
Answers.UserDisplayName: davejenx
Body: <p>A custom field was originally created as HTML type CheckBox (with Options Per Line set). This was later changed to type Select, using the <em>Change Input Field Type</em> facility in the Edit Field form. After this change, the field fails to appear in edit forms: the label displays but the Select field is  missing.</p>
  
Tags: <custom-fields><forms>
Title: Why is a custom field not appearing in forms after changing its type from CheckBox to Select?
ThreadText: # Why is a custom field not appearing in forms after changing its type from CheckBox to Select?
  
  (Asked by: username_0 on 2021-06-25)
  
  A custom field was originally created as HTML type CheckBox (with Options Per Line set). This was later changed to type Select, using the *Change Input Field Type* facility in the Edit Field form. After this change, the field fails to appear in edit forms: the label displays but the Select field is missing.
  
  **Tags:** custom-fields, forms
  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_0 on 2021-06-25. Score: 2
  
  I found that if a Select field has `options_per_line` set in `civicrm_custom_field`, then it fails to render, as described. A workaround is to unset Options Per Line in the UI before changing the field type, or set `options_per_line` to NULL in the database. The Select field then renders as it should.
  
  
  ---
  
  