topic Re: Publishing failed: Field Length is too short 20 in ArcGIS Survey123 Questions

Publishing failed: Field Length is too short 20

JordanMiller4 — Tue, 20 Mar 2018 15:30:19 GMT

I created a new survey using a Feature Service and I am getting the following error when I try to publish the survey. I assume the error is asking me to add additional characters to the field name but if I do that it won't capture the data back to the correct field.

Error:

The Custom feature service submission url is not compatible with the survey (Field ODERCOMPLAINTNUMBER in NEO Gas Leak length is too short 20.)

Img attached:

Re: Publishing failed: Field Length is too short 20

Anonymous User — Wed, 21 Mar 2018 00:52:05 GMT

Hi Jordan,

What is the exact field name, type and length when you check the existing feature service rest endpoint? Can you take a screenshot of that?

Can you also please share a copy of your xlsx form so we can take a closer look. I notice that you have duplicate fields names in the name column, which is also not supported.

Phil.

Re: Publishing failed: Field Length is too short 20

JordanMiller4 — Wed, 21 Mar 2018 13:54:33 GMT

Hi Philip,

I've attached our form below. Thanks!

Re: Publishing failed: Field Length is too short 20

EricBitner — Thu, 03 May 2018 18:12:23 GMT

Did you ever solve this? I am having a similar issue.

Mine says:

The custom feature service submission url is not compatible with this survey

(Field traptype in sitelocations length is too short 3

Re: Publishing failed: Field Length is too short 20

JordanMiller4 — Thu, 03 May 2018 18:32:03 GMT

Hi Eric, I haven't found a solution. Hopefully someone will come across this post and help us.

Re: Publishing failed: Field Length is too short 20

JamesTedrick — Thu, 03 May 2018 19:15:02 GMT

Hi Jordan,

The error indicates there is a mismatch between the length of characters allowed to be submitted and what the existing feature service can support. When creating a survey from an existing feature service, Survey123 Connect will normally write those values in the bind::esri:fieldLength column. As Phil suggested, looking at the REST endpoint (also called service URL in the ArcGIS Online/Enterprise web UI) will provide the appropriate values.

Re: Publishing failed: Field Length is too short 20

EricBitner — Fri, 04 May 2018 11:43:53 GMT

James,

I see in the service URL where is states length as 3 (the error I am receiving when I try to publish the survey. The survey publishes correctly but fails when I add a choice_filter. How is the choice filter affecting the publishing? The filter works and limits the choices on Survey 123 Connect but as mentioned it will not publish when the choice filter is applied.

Here is the choice filter:

filter_value=${commodity}

Re: Publishing failed: Field Length is too short 20

JamesTedrick — Mon, 07 May 2018 20:45:08 GMT

Hi Eric,

It appears that Survey123 is not properly reading the field length - can you manually set that to 3 in the bind::esri:esriFieldLength column?

Re: Publishing failed: Field Length is too short 20

ShawnRoberts1 — Tue, 18 Sep 2018 19:40:06 GMT

Hi James, I have kind of a similar question. I have a select_one that seems to have set the default value to 8 characters. I'm assuming that came from the max length of the choices available, as I never originally set it. This worked for round 1 of the surveys.

However now I need to add in more options that are longer than 8 characters, and when I attempt to publish I get the error that the field won't support the new length. I've tried setting the bind:fieldlength to 255, but that doesn't seem to work and still gives me the error.

(form with binding length set)

(Error)

Thanks,
Shawn.

Re: Publishing failed: Field Length is too short 20

JamesTedrick — Tue, 18 Sep 2018 20:26:17 GMT

Hi Shawn,

You are right about what most likely occurred. Unfortunately, the field length is not alterable once published. What you can do instead (using ArcGIS Online or ArcGIS Pro):

1) Add a column to temporarily store the existing answers

2) Calculate the values in the existing choice column to the temporary column

3) Delete the existing field

4) Add a new field with the same name

5) Calculate back the existing values from the temporary column to the new column

6) Delete the temporary column

Re: Publishing failed: Field Length is too short 20

Anonymous User — Thu, 20 Sep 2018 17:20:53 GMT

Hi James-

We got the error that the field name was too short so we followed your steps above using ArcGIS Pro. After the completing the steps we re-published the survey. ArcGIS online now has 2 hosted feature layers with the same name. The original survey data has 1142 records and length of the field is correct(we went from 7 to 10 text). The new (duplicate) survey data layer is empty with the field defined as 255 characters. We added a new record and this record shows up in the duplicate survey data instead of in the survey data that contains the other 1142 records.

Please help!

Re: Publishing failed: Field Length is too short 20

JamesTedrick — Fri, 21 Sep 2018 01:04:42 GMT

Hi Vivi,

Did you see any messages when publishing the survey? Has this survey already been shared for analysis (has a _stakeholder view)?

Re: Publishing failed: Field Length is too short 20

MartieClemons — Fri, 21 Sep 2018 17:34:39 GMT

Hi, James - I'm replying with regard to Vivi's questions. The survey does have a stakeholder view but I don't think it was shared for analysis so I'm not sure why it was created at the start. Since we can't figure out what happened, after collecting is done for the day, I'm going to export both surveys into file gdb's and combine using these instructions from Jennifer this morning: https://support.esri.com/en/technical-article/000001056, then publish the resulting comprehensive feature class with related comprehensive attachment table to AGO as a new feature service, then create a new survey in Connect and choose the new feature service and it should create a new survey which we'll then publish from Connect.