topic Re: Operation rolled back error in ArcGIS Survey123 Questions

Operation rolled back error

JürgenBiendara1 — Wed, 21 Nov 2018 16:02:35 GMT

Hello,

I get an "Operation rolled back" error with my survey. The survey was working in Connect version 3.0.127. Now I have updated to version 3.1.126, copied the survey and published it anew. The excerpt from the log file reads:

<15>1 2018-11-21T15:52:10Z DUROWA Survey123forArcGIS 32648 - [AppStudio@11205 category="qml" function="onSuccess" filename="XFormFeatureService.qml" line="726"] qml: applyEdits:errors: [
{
"code": 1003,
"description": "Operation rolled back.",
"tableId": 0
},
{
"code": 1000,
"description": "The INSERT statement conflicted with the FOREIGN KEY constraint \"REL_FK_service_c64e490357c146a98212a0ee53a91a7d_R_CRS_1\". The conflict occurred in database \"db_4886\", table \"user_4886.service_c64e490357c146a98212a0ee53a91a7d_R_TNK_TANK\", column 'globalid'.\r\nThe statement has been terminated.",
"tableId": 3
}
]
<15>1 2018-11-21T15:52:10Z DUROWA Survey123forArcGIS 32648 - [AppStudio@11205 category="qml" function="onFailed" filename="SubmitSurveysPage.qml" line="351"] qml: Feature service error: [
{
"code": 1003,
"description": "Operation rolled back.",
"tableId": 0
},
{
"code": 1000,
"description": "The INSERT statement conflicted with the FOREIGN KEY constraint \"REL_FK_service_c64e490357c146a98212a0ee53a91a7d_R_CRS_1\". The conflict occurred in database \"db_4886\", table \"user_4886.service_c64e490357c146a98212a0ee53a91a7d_R_TNK_TANK\", column 'globalid'.\r\nThe statement has been terminated.",
"tableId": 3
}
]
<15>1 2018-11-21T15:52:10Z DUROWA Survey123forArcGIS 32648 - [AppStudio@11205 category="qml" function="" filename="XFormsDatabase.qml" line="363"] qml: updateStatus: {
"rowsAffected": 1,
"insertId": "14",
"rows": {}
}
<15>1 2018-11-21T15:52:10Z DUROWA Survey123forArcGIS 32648 - [AppStudio@11205 category="qml" function="onFeatureServiceInfoChanged" filename="XFormFeatureService.qml" line="936"] qml: featureServiceInfo: null
<14>1 2018-11-21T15:52:10Z DUROWA Survey123forArcGIS 32648 - [AppStudio@11205 category="ArcGIS.AppFramework.Network"] ArcGIS.AppFramework.Network: NetworkNotifier: con: 66
<14>1 2018-11-21T15:52:10Z DUROWA Survey123forArcGIS 32648 - [AppStudio@11205 category="ArcGIS.AppFramework.Network"] ArcGIS.AppFramework.Network: NetworkNotifier: con: 66
<15>1 2018-11-21T15:52:10Z DUROWA Survey123forArcGIS 32648 - [AppStudio@11205 category="qml" function="update" filename="FilteredListModel.qml" line="62"] qml: Empty filterText
<12>1 2018-11-21T15:52:10Z DUROWA Survey123forArcGIS 32648 - [AppStudio@11205 category="default" filename="XFormWebhooks.qml" line="102"] qrc:/qml/XForms/XFormWebhooks.qml:102: TypeError: Cannot read property 'itemId' of null
<15>1 2018-11-21T15:52:13Z DUROWA Survey123forArcGIS 32648 - [AppStudio@11205 category="qml" function="editSubmitError" filename="SurveysListPage.qml" line="622"] qml: error: {
"code": 1003,
"description": "Operation rolled back.",
"tableId": 0
}
<15>1 2018-11-21T15:52:27Z DUROWA Survey123forArcGIS 32648 - [AppStudio@11205 category="qml" function="expression for onStateChanged" filename="Portal.qml" line="214"] qml: Application state changed: 2

Can someone hint to where might be the problem?

Thank you very much, best regards,

Jürgen

Re: Operation rolled back error

JohnathanHasthorpe — Fri, 23 Nov 2018 11:20:30 GMT

Can you share the survey .xls you used to publish the survey? Thanks

Re: Operation rolled back error

JürgenBiendara1 — Mon, 26 Nov 2018 13:06:18 GMT

Hi Jonathan,

There is a difference in the behavior of the survey depending on if I use it in my local ArcGIS Enterprise environment or if I use it in our AGOL environment. I can publish the survey in both and I can successfully send data with the desktop version of Survey123 (3.1.158) to my local environment. The "operation rolled back" error only appears in the AGOL environment.

Please find the xls file and the debug log attached.

Best regards,

Jürgen

Re: Operation rolled back error

JohnathanHasthorpe — Tue, 27 Nov 2018 03:36:07 GMT

Hi Jurgen - can you confirm the version of Connect you are using? This looks to be a related to a bug that existed in an older version of the application.

Thanks

John

Re: Operation rolled back error

JürgenBiendara1 — Tue, 27 Nov 2018 07:00:57 GMT

Hi Johnathan - I've just upgraded Connect to version 3.1.126.

Regards,

Jürgen

Re: Operation rolled back error

JohnathanHasthorpe — Tue, 27 Nov 2018 22:58:22 GMT

Can you try to re-publish the survey in 3.1.126 and retest? If the issue persists can you share the created service with me via a group: jhasthorpe_survey123. I can't repro this issue using your survey, so would like to see if there are any differences.

Thanks

John

Re: Operation rolled back error

JürgenBiendara1 — Wed, 28 Nov 2018 09:29:50 GMT

Hi Johnathan,

The latest results were already the Connect 3.1.126 results. Another test rendered the same results. It's working with my local ArcGIS Enterprise and fails in our AGOL environment. You now should have access to the "ROSEN Tank AGOL" survey.

Best regards,

Jürgen

Re: Operation rolled back error

JohnathanHasthorpe — Thu, 29 Nov 2018 03:34:35 GMT

Hi Jürgen

This cause of the issue looks to be related to the fact that your nested repeats have been nested in groups.

Removing the groups and republishing resolves the submission error.

I have raised a bug to a get this looked at.

Thanks

John

Re: Operation rolled back error

JürgenBiendara1 — Thu, 29 Nov 2018 08:56:38 GMT

Thank you very much, Johnathan, for the analysis. I can verify that removing the group elements from around the repeats solves the submission issue.
Let's see what development says. I, for my part, am convinced that this combination of repeats and groups (which works fine in an ArcGIS Enterprise environment) is indispensable for a well structured and clearly laid out survey and should also work in AGOL.

Best regards,

Jürgen

Re: Operation rolled back error

Anonymous User — Tue, 15 Jan 2019 02:48:29 GMT

Hi Jurgen,

Just an update to let you know that we have been working on the issues described in this post and a lot of progress has been made with repeats/nested repeats and defaults/calculations/relevants/groups and missing values when opening the survey, so we believe the issue has been resolved for our upcoming 3.2 release which is due end of January.

If you have time, can you please check out the latest 3.2 RC builds (Connect 3.2.192 and App 3.2.262) available on EAC here: Welcome to our Feedback Community and provide any feedback. The sooner we can get feedback the sooner we can address any outstanding issues before the release.

Regards,

Phil.

Re: Operation rolled back error

JW_Mapguy — Mon, 23 Mar 2020 21:55:04 GMT

I'm still getting that error message and I've extensively done some testing and debugging. I narrowed it down to two select multiple questions, this survey does not like having two, despite the fact that I removed the constraint on them, removed all spaces and special characters in the names list in the choices tab, and basically trimmed my survey down to almost nothing. Still not sure why I am getting this error. James Tedrick‌ any ideas?

Re: Operation rolled back error

JamesTedrick — Tue, 24 Mar 2020 18:25:06 GMT

Hi John,

Just to check, did you alter the field length in the form after initial publishing (what does the feature service report as the field length)? Unfortunately, altering the field length in the form after initial field creation cannot alter the field length - you would need to delete the fields in the feature service and have added again (either through Survey123 Connect or manually).