Answers.Body: <p>For the interim to let exports work, I have made the DB Field Length match the longest field label.</p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2020-02-10T16:56:52.610Z
Answers.LastActivityDate: 2020-02-10T19:10:23.890Z
Answers.LastEditDate: 2020-02-10T19:10:23.890Z
Answers.UserDisplayName: Andy Burns
Body: <p>The error is e.g.</p>
  
  <blockquote>
    <p>Data too long for column 'custom_194' at row 1</p>
  </blockquote>
  
  <p>Our values are 1 character so we set the DB Field Length to 1. However, this makes exports of this same field fail. It is exporting the label, not the value, so DB Field Length needs to accommodate the label. </p>
  
  <p>Since this is unresolved <a href="https://lab.civicrm.org/dev/core/issues/181" rel="nofollow noreferrer">https://lab.civicrm.org/dev/core/issues/181</a> is setting a longer DB Field Length my only alternative to letting exports work again? </p>
  
Tags: <custom-fields><export>
Title: Data too long for column breaks export
ThreadText: # Data too long for column breaks export
  
  (Asked by: username_0 on 2020-02-10)
  
  The error is e.g.
  
  > Data too long for column 'custom\_194' at row 1
  
  Our values are 1 character so we set the DB Field Length to 1. However, this makes exports of this same field fail. It is exporting the label, not the value, so DB Field Length needs to accommodate the label.
  
  Since this is unresolved <https://lab.civicrm.org/dev/core/issues/181> is setting a longer DB Field Length my only alternative to letting exports work again?
  
  **Tags:** custom-fields, export
  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_0 on 2020-02-10. Score: 2 | Accepted answer
  
  For the interim to let exports work, I have made the DB Field Length match the longest field label.
  
  
  ---
  
  