Error 1000 from Survey123

[CandiceOoi]

Hi all,

I encountered an error when I wanted to submit a survey form using the Survey123 App. I have been using the form for a while and have not encountered an error previously. I received an Error Code 1000, stating "String or binary data would be truncated. The statement has been terminated.".

I referred to several links below and couldn't figure out the reason why this happened. I do not have any select_multiple questions in my form.  I am using Survey123 Connect version 2.6.6 and Survey123 version 2.6.9.

I truly appreciate if anyone finds a solution to this. Thank you very much. 

https://community.esri.com/groups/survey123/blog/2017/08/30/understanding-multiple-choice-questions-... 

Send Error- Code 1000 

https://community.esri.com/thread/174329?q=code%201000 

https://community.esri.com/thread/177525#comment-610451 

[JamesTedrick]

Hi Candice,

This error occurs when a text answer is longer than the field can store.  Aside from typing in a long-is answer (the default storage size for text questions is 255 characters), this can also occur if a survey has been republished with a select one choice whose name is longer than the original choices (this scenario will be fixed for surveys published by the next release of Survey123).

[CandiceOoi]

Hi James Tedrick‌,

Thank you for getting back to me. So the only solution is to ensure the current choices are shorter than the previous ones before the form is republished? I duplicated the forms (using the same spreadsheet) and published it as a new survey. However, Survey123 seems to "remember" what my previous choices are in the previous survey because I wasn't able to submit the form. 

[Anonymous User]

Would you potentially be able to override the column "length" of the question that is storing your answer by adjusting the "bind::esri:fieldLength" to a value that is larger than the longest answer for a select_one question.

Meaning, if you have a select one question that contains an answer that is 400 characters, then you would set the "bind::esri:fieldLength" value to 425, so that selection is not truncated. This has helped me out in the past.