Body: <p>Running Drupal 7.94/CiviCRM 5.57</p>
  <p>I've created a custom field for an activity that contains 5,000 choices. Seems to work fine on the CiviCRM Admin side, but when I add that same field to a Webform I get this error:</p>
  <p>&quot;PDOException: SQLSTATE[22001]: String data, right truncated: 1406 Data too long for column 'extra' at row...&quot;</p>
  <p>What would be an effective manner to correct this?</p>
  
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2023-01-17T16:11:33.767Z
Comments.Text: 5000 choices!  Just wondering whether there is a better way to structure that.  What's the goal?
Comments.UserDisplayName: Aidan
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2023-01-17T17:09:46.450Z
Comments.Text: Is this of type multi-select or checkbox?
Comments.UserDisplayName: Pradeep Nayak
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2023-01-17T21:08:31.540Z
Comments.Text: Type is Autocomplete-Select.
  
  The field collects which law a contact is suspected of being arrested for.  The dataset contains 5600 total laws. I can likely trim that down to 2600 but I still get the same error.
Comments.UserDisplayName: V3rmie
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2023-01-18T01:43:00.720Z
Comments.Text: we have approached this previously by creating a specific table, and folk choose from that, and then (from memory) the form pushes that value in to a simple txt field in civi
Comments.UserDisplayName: petednz - fuzion
Tags: <custom-fields><fieldoptions>
Title: Can I have more than 5000 options for a custom field?
ThreadText: # Can I have more than 5000 options for a custom field?
  
  (Asked by: username_0 on 2023-01-17)
  
  Running Drupal 7.94/CiviCRM 5.57
  
  I've created a custom field for an activity that contains 5,000 choices. Seems to work fine on the CiviCRM Admin side, but when I add that same field to a Webform I get this error:
  
  "PDOException: SQLSTATE[22001]: String data, right truncated: 1406 Data too long for column 'extra' at row..."
  
  What would be an effective manner to correct this?
  
  **Tags:** custom-fields, fieldoptions
  
  > **Comments:**
  > **username_1**: 5000 choices!  Just wondering whether there is a better way to structure that.  What's the goal?  
  > **username_2**: Is this of type multi-select or checkbox?  
  > **username_0**: Type is Autocomplete-Select.  The field collects which law a contact is suspected of being arrested for.  The dataset contains 5600 total laws. I can likely trim that down to 2600 but I still get the same error.  
  > **username_3**: we have approached this previously by creating a specific table, and folk choose from that, and then (from memory) the form pushes that value in to a simple txt field in civi  
  
  ---
  
  ## 0 answers
  
  