Latest Contributions by ChristopherVan_de_Wyngard

We are experiencing a production issue with a long-running Survey123 survey whose parent hosted feature layer contains 907 fields and currently has approximately 503 records. The survey and feature layer worked previously, but multiple Survey123 and ArcGIS Online functions recently began failing with the following error: Cannot perform query. Invalid query parameters. 'SQL query is nested too deeply. Rewrite the query or break it up into smaller queries.' parameter is invalid Error Code: 400 We performed controlled testing through the ArcGIS REST Services Directory to isolate the problem. Controlled REST query results Test settings: where=1=1 returnGeometry=false resultRecordCount=1 Request method=POST Results: 796 explicitly requested fields = succeeds 797 explicitly requested fields = fails 907 fields / outFields=* = fails We tested multiple different field combinations rather than only the first fields in the schema. The following all succeeded: First 796 fields Last-heavy combination of 796 fields Middle-field combination of 796 fields Split beginning/end combination of 796 fields Evenly distributed 796 fields Multiple randomized combinations of 796 fields Multiple different combinations containing exactly 797 fields failed with the same nested-SQL error. We also tested the field located at position 797: That field works when requested by itself. The first 795 fields plus that field also work because the total is 796. Therefore, we have not identified a particular defective field. The failure appears to be based on the total number of requested fields. Survey123 Field App Inbox refresh fails with: Cannot perform query. Invalid query parameters. Code 400 We tested two different Field App versions, and both produced the same result: Survey123 Field App 3.1 Survey123 Field App 3.25 Survey123 website The Survey123 Data page recognizes the record count and displays approximately: 503/503 However, the attribute table is blank. Because the rows contain no visible data, records cannot be selected for report generation. ArcGIS Map Viewer The parent-layer geometries and record count load, but the attribute table is blank. Using Chrome Developer Tools, we confirmed the attribute table sends this query: where=1=1 outFields=* returnGeometry=false resultRecordCount=50 f=pbf Because outFields=* requests all 907 fields, the table does not populate. A configured Map Viewer pop-up still works. We captured its requested field list and confirmed that it requests only 201 fields, not all 907. Survey123 Feature Report service A report request for one specific record was submitted successfully and received a valid job ID. The job then failed during preparation: jobStatus: esriJobFailed detailedStatus: prepareFailed progress: 0 The report request was limited to one ObjectID: "queryParameters": { "objectIds": "5068"} The returned message was: An error occurred when querying data from the feature layer. 400: Cannot perform query. Invalid query parameters. 'SQL query is nested too deeply. Rewrite the query or break it up into smaller queries.' parameter is invalid This occurred before the Word document was created. ArcGIS API for Python A custom Python export process also failed while querying the same single parent record with: ft.query( where="objectid=5068", out_fields="*", return_geometry=False) The ArcGIS API for Python returned the same Code 400 and nested-SQL error. Changing the Python process so it requests only the ObjectID and GlobalID allows it to avoid that specific full-width query. Confirmed behavior summary Operation Requested fields Result REST query 796 Succeeds REST query 797 Fails REST query * / 907 Fails Map Viewer pop-up 201 Succeeds Map Viewer attribute table * / 907 Blank Survey123 Data page Full parent schema Blank Survey123 Inbox Full parent schema Code 400 Feature Report for one ObjectID Full parent record preparation Fails Python query with out_fields="*" 907 Fails Questions for Esri Is there a known ArcGIS Online or Survey123 issue that causes hosted feature-layer queries to fail when 797 or more fields are requested? Has there been a recent backend or query-processing change that could explain why this survey worked previously with the same schema? Is the 796/797 boundary associated with a known defect? Can Esri review the hosted service logs to determine why the generated query is considered “nested too deeply”? Is there a supported workaround for Survey123 Inbox, the Data page, and Feature Reports other than rebuilding the survey with fewer parent-layer fields? Can these Survey123 operations be changed to request attributes in smaller batches rather than using the complete parent schema? At this time, the only confirmed distinction is that operations requesting a limited field list continue to work, while operations requesting 797 or more fields fail. ... View more

We are experiencing a production issue with a long-running Survey123 survey whose parent hosted feature layer contains 907 fields and currently has approximately 503 records. The survey and feature layer worked previously, but multiple Survey123 and ArcGIS Online functions recently began failing with the following error: Cannot perform query. Invalid query parameters. 'SQL query is nested too deeply. Rewrite the query or break it up into smaller queries.' parameter is invalid Error Code: 400 We performed controlled testing through the ArcGIS REST Services Directory to isolate the problem. Controlled REST query results Test settings: where=1=1 returnGeometry=false resultRecordCount=1 Request method=POST Results: 796 explicitly requested fields = succeeds 797 explicitly requested fields = fails 907 fields / outFields=* = fails We tested multiple different field combinations rather than only the first fields in the schema. The following all succeeded: First 796 fields Last-heavy combination of 796 fields Middle-field combination of 796 fields Split beginning/end combination of 796 fields Evenly distributed 796 fields Multiple randomized combinations of 796 fields Multiple different combinations containing exactly 797 fields failed with the same nested-SQL error. We also tested the field located at position 797: That field works when requested by itself. The first 795 fields plus that field also work because the total is 796. Therefore, we have not identified a particular defective field. The failure appears to be based on the total number of requested fields. Survey123 Field App Inbox refresh fails with: Cannot perform query. Invalid query parameters. Code 400 We tested two different Field App versions, and both produced the same result: Survey123 Field App 3.1 Survey123 Field App 3.25 Survey123 website The Survey123 Data page recognizes the record count and displays approximately: 503/503 However, the attribute table is blank. Because the rows contain no visible data, records cannot be selected for report generation. ArcGIS Map Viewer The parent-layer geometries and record count load, but the attribute table is blank. Using Chrome Developer Tools, we confirmed the attribute table sends this query: where=1=1 outFields=* returnGeometry=false resultRecordCount=50 f=pbf Because outFields=* requests all 907 fields, the table does not populate. A configured Map Viewer pop-up still works. We captured its requested field list and confirmed that it requests only 201 fields, not all 907. Survey123 Feature Report service A report request for one specific record was submitted successfully and received a valid job ID. The job then failed during preparation: jobStatus: esriJobFailed detailedStatus: prepareFailed progress: 0 The report request was limited to one ObjectID: "queryParameters": { "objectIds": "5068"} The returned message was: An error occurred when querying data from the feature layer. 400: Cannot perform query. Invalid query parameters. 'SQL query is nested too deeply. Rewrite the query or break it up into smaller queries.' parameter is invalid This occurred before the Word document was created. ArcGIS API for Python A custom Python export process also failed while querying the same single parent record with: ft.query( where="objectid=5068", out_fields="*", return_geometry=False) The ArcGIS API for Python returned the same Code 400 and nested-SQL error. Changing the Python process so it requests only the ObjectID and GlobalID allows it to avoid that specific full-width query. Confirmed behavior summary Operation Requested fields Result REST query 796 Succeeds REST query 797 Fails REST query * / 907 Fails Map Viewer pop-up 201 Succeeds Map Viewer attribute table * / 907 Blank Survey123 Data page Full parent schema Blank Survey123 Inbox Full parent schema Code 400 Feature Report for one ObjectID Full parent record preparation Fails Python query with out_fields="*" 907 Fails Questions for Esri Is there a known ArcGIS Online or Survey123 issue that causes hosted feature-layer queries to fail when 797 or more fields are requested? Has there been a recent backend or query-processing change that could explain why this survey worked previously with the same schema? Is the 796/797 boundary associated with a known defect? Can Esri review the hosted service logs to determine why the generated query is considered “nested too deeply”? Is there a supported workaround for Survey123 Inbox, the Data page, and Feature Reports other than rebuilding the survey with fewer parent-layer fields? Can these Survey123 operations be changed to request attributes in smaller batches rather than using the complete parent schema? At this time, the only confirmed distinction is that operations requesting a limited field list continue to work, while operations requesting 797 or more fields fail. ... View more

How can I edit the attachment tables of my Survey123 survey in ArcGIS Pro. Can anyone provide a step-by-step guide on how to do this? Specifically, I want to know how to view and then edit data in the attachment tables and ensure that my changes are reflected in the related records in the main survey form. Any tips or best practices for editing attachment tables in ArcGIS Pro would be appreciated. ... View more

Does Survey123 have a built-in "Track Changes" feature like Microsoft Word to be able to track data changes and be able to see the changes to the data, and to then be able to approve or deny these changes.  ... View more