topic Re: String or binary data would be truncated Send Error in ArcGIS Survey123 Questions

String or binary data would be truncated Send Error

maoneill9 — Wed, 09 Nov 2022 13:19:11 GMT

I am getting an error when trying to submit a survey via Survey123. The error reads "String or binary data would be truncated". I have tried to change the "bind::esifieldLength" of some fields with no success. I also did not build this survey which is making it hard to troubleshoot and the person who built it no longer works here.

The survey excel sheet is attached and any input would be greatly appreciated!

Re: String or binary data would be truncated Send Error

DougBrowning — Wed, 09 Nov 2022 14:40:07 GMT

You increased the field size on each begin repeat line. Repeats are not fields so that does not do anything. Repeats are the tables. You need to change the field length on the text field that is causing the issue. My guess would be one of the Notes lines. The error that pops up or the log file should tell you the exact field that has the issue. You can also look at the form and you will probably see which field has more than the 255 default char length.

Hope that helps

Re: String or binary data would be truncated Send Error

maoneill9 — Wed, 09 Nov 2022 15:35:14 GMT

When I receive the error it does not specify which field is responsible, nor does the log show anything about the send error. I have tried to change the lengths of all the text fields, but when I attempt to publish the survey I receive an error saying " Existing feature service is not compatible with the survey. Field swale_notes in swale_group length is too short 255).

Thanks for the tips. I am fairly new to Survey123 so I appreciate the help.

Re: String or binary data would be truncated Send Error

DougBrowning — Wed, 09 Nov 2022 15:49:06 GMT

Is this built off an existing service? If not and you have no data you can let it overwrite the service. If it is then changing it can tough but you can try it in the service.

Basically you are trying to put too much text in one of the notes fields. Either make the field bigger or do not put so much text in. You could use string-length to limit it in a constraint. If you have a form that is already there and will not submit have the user reduce any text fields to 255.

Hope that helps

Re: String or binary data would be truncated Send Error

maoneill9 — Wed, 09 Nov 2022 16:41:45 GMT

Thanks for the help! It was actually a problem with my select_multiple fields and I was able to solve it by setting the field length to 1000 and republishing the service.

Re: String or binary data would be truncated Send Error

AndrewSmeltz — Thu, 23 May 2024 14:32:11 GMT

How did you determine which field was causing the issue?

Were you are able to edit and update the survey without republishing and overwriting the existing hosted feature service?

Thanks! I am having the same issue.

Re: String or binary data would be truncated Send Error

ALESSANDRASPREAFICO — Fri, 28 Mar 2025 08:31:11 GMT

I wasn't able to determine which field is responsible for the error.

I noticed that the field with multiple selection has a limit of 1000 characters. This is visible when you publich the survey and you click on "modify schema" button.

The field with multiple selections stores the multiple replies in a single field, but there's an automatic reduction of the text. If you observe the data in the table, this is visible, but if you query the point, in the pop-up and in the report you see the full text.

I noticed that in the multiple selections fields when you enable 'other' option, the lenght is 1000 for the field and 255 for the 'other'. The other is stored in a separate field.

I hope this helps other users in understanding which field is responsible for the error during submission.

Re: String or binary data would be truncated Send Error

DarrylKlassen1 — Fri, 09 May 2025 19:59:16 GMT

I have had the same error when calculating a field in ArcGIS Online feature service with a string - the string entered was too long and it gave me this error. I was using VertiGIS Workflow to do the calculation, so had trouble identifying the exact problem, but it turned out to be the same solution - make the field longer or enter short text. Just adding his as it might be helpful to others who are searching for it.