Survey123 submission "Getting service information" stuck reading related table

[GeospatialManagement]

I have a featureclass (checkpoints) which has its geometry defined in Workforce, and is populated using Survey123. The featureclass also has a related table that will use Survey123 to populated records (log of vehicles at checkpoints). 

When I try to submit a completed survey, either on the featureclass or related record I encounter an issue when "Getting service information" on the related record, which halts progress.

Is this a known issue, and does it have a fix?

Thank you.

[SeanLavallee__MES_]

We have been testing submission and have not been able to get one survey to submit. I've changed my form because I read a thread about having Repeat Group-Images hanging up surveys, but it will still spin. My photos only interact with users when Relevant field is activated. Still no success, it just spins for hours and hours. Even surveys with not pictures won't go through. Lost on any other changes...

I emailed and attached latest log I received.

[DougBrowning]

I cannot tell which version you are using but every time this happened to me it was due to have a nested repeat.  That should work now but if you have an older version this may be it.

You cannot have anything that is 3 levels deep at all.  So if you have a table that has attachments off of it - you will get this error.

[KyleGjeruldsen]

I finally got mine fixed by going into my MXD and assigning my linked table with a unique layer id of 0 and my feature class with a layer id of 1 and recreated my feature service.  It now works.

[DougBrowning]

Well this one just got me again today.  No idea what it is this time.  Is there any way to find clues or just good luck?

It all ran fine in test.  Created a new copy and then stuck on Getting Service info again.

Thanks

[DougBrowning]

Looks like it is trying to do something with my other Relationship classes and saying unsupported.

But the Failed 300d is something.  What does that mean?

QEGLPlatformContext: eglSwapBuffers failed: 300d

<15>1 2019-04-19T20:15:32Z localhost Survey123forArcGIS 22814 - [AppStudio@11205 category="qml" function="updateRelationships" filename="XFormFeatureService.qml" line="1180"] qml: Updating relationship for: Plots
<15>1 2019-04-19T20:15:32Z localhost Survey123forArcGIS 22814 - [AppStudio@11205 category="qml" function="updateRelationships" filename="XFormFeatureService.qml" line="1180"] qml: Updating relationship for: PlotCircle
<10>1 2019-04-19T20:15:32Z localhost Survey123forArcGIS 22814 - [AppStudio@11205 category="qml" function="updateChildRelationship" filename="XFormFeatureService.qml" line="1114"] qml: Unsupported childKeyField type: esriFieldTypeString
<15>1 2019-04-19T20:15:32Z localhost Survey123forArcGIS 22814 - [AppStudio@11205 category="qml" function="updateRelationships" filename="XFormFeatureService.qml" line="1180"] qml: Updating relationship for: Routes
<10>1 2019-04-19T20:15:32Z localhost Survey123forArcGIS 22814 - [AppStudio@11205 category="qml" function="updateChildRelationship" filename="XFormFeatureService.qml" line="1114"] qml: Unsupported childKeyField type: esriFieldTypeString
<15>1 2019-04-19T20:15:32Z localhost Survey123forArcGIS 22814 - [AppStudio@11205 category="qml" function="updateRelationships" filename="XFormFeatureService.qml" line="1180"] qml: Updating relationship for: LPI
<10>1 2019-04-19T20:15:32Z localhost Survey123forArcGIS 22814 - [AppStudio@11205 category="qml" function="updateChildRelationship" filename="XFormFeatureService.qml" line="1114"] qml: Unsupported childKeyField type: esriFieldTypeString
<15>1 2019-04-19T20:15:32Z localhost Survey123forArcGIS 22814 - [AppStudio@11205 category="qml" function="updateRelationships" filename="XFormFeatureService.qml" line="1180"] qml: Updating relationship for: Gap
<10>1 2019-04-19T20:15:32Z localhost Survey123forArcGIS 22814 - [AppStudio@11205 category="qml" function="updateChildRelationship" filename="XFormFeatureService.qml" line="1114"] qml: Unsupported childKeyField type: esriFieldTypeString
<15>1 2019-04-19T20:15:32Z localhost Survey123forArcGIS 22814 - [AppStudio@11205 category="qml" function="updateRelationships" filename="XFormFeatureService.qml" line="1180"] qml: Updating relationship for: SpeciesRichness
<10>1 2019-04-19T20:15:32Z localhost Survey123forArcGIS 22814 - [AppStudio@11205 category="qml" function="updateChildRelationship" filename="XFormFeatureService.qml" line="1114"] qml: Unsupported childKeyField type: esriFieldTypeString
<15>1 2019-04-19T20:15:32Z localhost Survey123forArcGIS 22814 - [AppStudio@11205 category="qml" function="updateRelationships" filename="XFormFeatureService.qml" line="1180"] qml: Updating relationship for: SoilStability
<10>1 2019-04-19T20:15:32Z localhost Survey123forArcGIS 22814 - [AppStudio@11205 category="qml" function="updateChildRelationship" filename="XFormFeatureService.qml" line="1114"] qml: Unsupported childKeyField type: esriFieldTypeString
<15>1 2019-04-19T20:15:32Z localhost Survey123forArcGIS 22814 - [AppStudio@11205 category="qml" function="updateRelationships" filename="XFormFeatureService.qml" line="1180"] qml: Updating relationship for: PlotObservation
<10>1 2019-04-19T20:15:32Z localhost Survey123forArcGIS 22814 - [AppStudio@11205 category="qml" function="updateChildRelationship" filename="XFormFeatureService.qml" line="1114"] qml: Unsupported childKeyField type: esriFieldTypeString
<15>1 2019-04-19T20:15:32Z localhost Survey123forArcGIS 22814 - [AppStudio@11205 category="qml" function="updateRelationships" filename="XFormFeatureService.qml" line="1180"] qml: Updating relationship for: PlotChar
<10>1 2019-04-19T20:15:32Z localhost Survey123forArcGIS 22814 - [AppStudio@11205 category="qml" function="updateChildRelationship" filename="XFormFeatureService.qml" line="1114"] qml: Unsupported childKeyField type: esriFieldTypeString
<15>1 2019-04-19T20:15:32Z localhost Survey123forArcGIS 22814 - [AppStudio@11205 category="qml" function="updateRelationships" filename="XFormFeatureService.qml" line="1180"] qml: Updating relationship for: KnownErrors
<10>1 2019-04-19T20:15:32Z localhost Survey123forArcGIS 22814 - [AppStudio@11205 category="qml" function="updateChildRelationship" filename="XFormFeatureService.qml" line="1114"] qml: Unsupported childKeyField type: esriFieldTypeString
<15>1 2019-04-19T20:15:32Z localhost Survey123forArcGIS 22814 - [AppStudio@11205 category="qml" function="updateRelationships" filename="XFormFeatureService.qml" line="1180"] qml: Updating relationship for: AIMPhotos
<10>1 2019-04-19T20:15:32Z localhost Survey123forArcGIS 22814 - [AppStudio@11205 category="qml" function="updateChildRelationship" filename="XFormFeatureService.qml" line="1114"] qml: Unsupported childKeyField type: esriFieldTypeString
<15>1 2019-04-19T20:15:32Z localhost Survey123forArcGIS 22814 - [AppStudio@11205 category="qml" function="updateRelationships" filename="XFormFeatureService.qml" line="1180"] qml: Updating relationship for: UnknownPlants
<10>1 2019-04-19T20:15:32Z localhost Survey123forArcGIS 22814 - [AppStudio@11205 category="qml" function="updateChildRelationship" filename="XFormFeatureService.qml" line="1114"] qml: Unsupported childKeyField type: esriFieldTypeString
<12>1 2019-04-19T20:15:32Z localhost Survey123forArcGIS 22814 - [AppStudio@11205 category="default" filename="XFormFeatureService.qml" line="1180"] qrc:/qml/XForms/XFormFeatureService.qml:1180: TypeError: Cannot read property 'name' of undefined
<15>1 2019-04-19T20:15:50Z localhost Survey123forArcGIS 22814 - [AppStudio@11205 category="default"] JNI: onPause: API 26+
<12>1 2019-04-19T20:15:50Z localhost Survey123forArcGIS 22814 - [AppStudio@11205 category="default"] QEGLPlatformContext: eglSwapBuffers failed: 300d
<15>1 2019-04-19T20:15:50Z localhost Survey123forArcGIS 22814 - [AppStudio@11205 category="qml" function="expression for onStateChanged" filename="Portal.qml" line="227"] qml: Application state changed: 0
<15>1 2019-04-19T20:15:50Z localhost Survey123forArcGIS 22814 - [AppStudio@11205 category="qml" function="expression for onStateChanged" filename="Portal.qml" line="227"] qml: Application state changed: 0

[JamesTedrick]

Hi Doug,

The QEGLPlatform context error is likely a red herring - that would be part of the graphics display system.  Can you provide the schema of the service?  It looks like there is a string-based relationship present; are there also GUID-based ones?

[DougBrowning]

Yes I have 9 forms - all with the original RCs (relationships classes).  Then I made 9 more that point from my master Points FC (for Collector) - these are the string ones.

It almost seems like 123 is assuming no other RCs will exist - and so when it finds them it gets mad.

Except that I did all of this last year no problem.  And in certain situations it will work.  In fact I have an exact clone that works just fine now. (after the remove _Attach, publish, readd, publish trick).

I have tried about 100 times, with dif ways, now.

So now again I just made a all new test project (mxd, service, the works). and still hangs.  Remove the _Attach tables - still hangs.  Remove ALL tables - still hangs.  Add the tables back in - works!  Huh?

Try doing this workflow to original service - nope still hangs.  It is just so inconsistent I am running out of ideas to try.

It has to be something with tables or the order things are added to the map.

I can share the whole thing with you if you can take a look.  What is your AGOL account again.

Thanks I am really up against the wall now.  Plus I have 2 more to do.  

[DougBrowning]

Ok so now I removed the _Attach tables from my map and republished and it starting working again??

It seems that photos and all that are still working somehow.  Should I not have _Attach in there.  My other service has it and works fine.  One last year did.

Ideas?  Thanks

Oh and all this republishing somehow breaks my web map!  So I get to recreate that 50 times now.  It just stops loading half the layers.  Prob cause their IDs keep changing.

I have lost 4 full days to this now.

[JamesTedrick]

In general, I would not recommend having the attachment tables exposed in the feature service - they are designed to be managed by the server automatically.

[DougBrowning]

They are not exposed.  They do not get listed anywhere or anything.  I figured they were still needed.

Does it just create them or something?  I can leave them off?  

Been having them in there for 3 years now so not sure why it suddenly is an issue.