SQL query is nested too deeply

[EdKnowles]

G'day All

Started receiving the above error message (in the Chrome console) from https://survey123.arcgis.com/ and https://maps.arcgis.com/ in the last 24 hrs.

Error message from the survey123 website is the same as this.

The survey has not changed in that time. Existing surveys have been edited.

Survey has been in use for a couple of years.

It's a long shot and has anything changed on the mentioned websites?

Thanks

Ed

[ChristopherVan_de_Wyngard]

We began experiencing what appears to be the same issue this week. Our long-running Survey123 parent layer has 907 fields. Controlled POST queries show that every tested combination of 796 fields succeeds, while every tested combination of 797 fields fails with “SQL query is nested too deeply.” Survey123 Inbox, the Data page, Map Viewer tables, and Feature Reports are all affected. Did you determine how many fields are in your parent layer?

[EdKnowles]

The survey has 808 fields.

I can also read data via the REST end point, if requesting a subset of fields.

I can see all fields if I view a single FID ie FeatureServer/0/1

I can still export the data to Excel via the Survey123 website.

[ChristopherVan_de_Wyngard]

Your results appear very similar to ours. The fact that your survey has 808 fields and subset queries work is especially significant.

The FeatureServer/0/1 URL uses the individual Feature resource rather than the layer’s /query operation, so it may explain why one feature can display all attributes while wide queries fail.

Could you test the following through FeatureServer/0/query using POST?

where=1=1
returnGeometry=false
resultRecordCount=1
f=json

Then test:

1. An explicit list of the first 796 fields
2. An explicit list of the first 797 fields
3. outFields=*

Our 907-field layer consistently succeeds with 796 fields and fails with 797. It would be very helpful to know whether your 808-field layer has the same boundary. Also, does your Excel export contain all 808 parent-layer columns?

[EdKnowles]

1. All good
2. SQL query is nested too deeply error
3. SQL query is nested too deeply error

The Excel export contains all columns

[EdKnowles · Accepted solution]

This has magically sorted itself out, for now 🙂