Latest Contributions by DougBrowning

Why not draw the Polygon in Collector then launch Survey123 via a URL to keep them linked? Just an idea. ... View more

I would suggest using a different workflow.  Make a new form for each visit.  That way you have full editor tracking and all that (day, time, who visited, etc) .  Plus they can copy over from the last visit make a few changes then submit. Then have a FC of trap locations.  Create a relationship class between the FC and the visit form.  Now you can click a point and see all the visits (without dealing with a level down relate). Then if you really want to get fancy load the trap points in collector with all the base fields.  Then launch Survey123 from Collector - using URLs to fill out the header.  Now you have a full connected workflow.  See this post for more page 7 - https://community.esri.com/groups/survey123/blog/2016/07/30/understanding-survey123s-custom-url-scheme?messageTarget=all&start=150&mode=comments Just a thought - we changed to this style of one form per visit vs one form for all and there are a lot of advantages. Hope it helps. ... View more

I believe they posted once that it will be in the new Aurora build.  For me I used a field called FormID and put the form item id in it.  Then it is just a To prefill the Form with the ID from collector use the URL thing like this arcgis-survey123://?itemID={PlotCharForm}&field:SiteKey={SiteKey}&field:PlotKey={PlotID} ... View more

I used all text fields and it worked fine.  So I would try that.  I was using a Plot ID and not any global ids. ... View more

You cannot use Arcade in Collector.  I tried also but it is a known limitation. ... View more

This is a known bug that I logged.  It does it in the attribute table also.  They fixed the table in 10.5 but I do not think they fixed the layout part yet. ... View more

I get this ['nom', 'pointLayer', 'surveyGeo', 'whereClause', '__builtins__', 'fields', '__file__', '__package__', 'sys', 'arcgis', 'time', '__name__', 'datetime', 'arcpy', '__doc__', 'math'] But with no name what am I looking for? Thanks ... View more

I sent you the form Friday morning - did you not get it? Yes the issue went away when I took out the Default values on the select_one.  On this form I can break it at will using the default values.  Not sure why I think I have done that before.  If you figure out why let me know. Thanks ... View more

Well it turned out to be a bad GDB I guess.  Created a new GDB, copied the same FCs over, published, all worked. Weird ... View more

I think we traced it down to having a Default value on a Select_one list.  Sound right? ... View more

Connect is 2.5.44 ( I am locked into that). Windows 10 form app 2.6.9 Android App 2.6.9 Yes send me your email I cannot post it. Thanks! ... View more

James Tedrick‌ Finally got a log file to work.  It seems to be complaining about Relationships and string type?  Also suddenly export works.  I noticed in the exported GeoDB it changed the names of all the survey123 relates.  They were something like Group_repeat and after export they are Formname_19. Also this error  TypeError: Cannot read property 'name' of undefined Thanks <15>1 2018-03-29T17:37:03Z localhost Survey123forArcGIS 26697 - [AppStudio@11205 category="qml" function="updateRelationships" filename="XFormFeatureService.qml" line="876"] qml: Updating relationship for: Plots <15>1 2018-03-29T17:37:03Z localhost Survey123forArcGIS 26697 - [AppStudio@11205 category="qml" function="updateRelationships" filename="XFormFeatureService.qml" line="876"] qml: Updating relationship for: AIMPhotos <10>1 2018-03-29T17:37:03Z localhost Survey123forArcGIS 26697 - [AppStudio@11205 category="qml" function="updateChildRelationship" filename="XFormFeatureService.qml" line="810"] qml: Unsupported childKeyField type: esriFieldTypeString <15>1 2018-03-29T17:37:03Z localhost Survey123forArcGIS 26697 - [AppStudio@11205 category="qml" function="updateRelationships" filename="XFormFeatureService.qml" line="876"] qml: Updating relationship for: GAP <10>1 2018-03-29T17:37:03Z localhost Survey123forArcGIS 26697 - [AppStudio@11205 category="qml" function="updateChildRelationship" filename="XFormFeatureService.qml" line="810"] qml: Unsupported childKeyField type: esriFieldTypeString <15>1 2018-03-29T17:37:03Z localhost Survey123forArcGIS 26697 - [AppStudio@11205 category="qml" function="updateRelationships" filename="XFormFeatureService.qml" line="876"] qml: Updating relationship for: KnownErrors <10>1 2018-03-29T17:37:03Z localhost Survey123forArcGIS 26697 - [AppStudio@11205 category="qml" function="updateChildRelationship" filename="XFormFeatureService.qml" line="810"] qml: Unsupported childKeyField type: esriFieldTypeString <15>1 2018-03-29T17:37:03Z localhost Survey123forArcGIS 26697 - [AppStudio@11205 category="qml" function="updateRelationships" filename="XFormFeatureService.qml" line="876"] qml: Updating relationship for: LPI <10>1 2018-03-29T17:37:03Z localhost Survey123forArcGIS 26697 - [AppStudio@11205 category="qml" function="updateChildRelationship" filename="XFormFeatureService.qml" line="810"] qml: Unsupported childKeyField type: esriFieldTypeString <15>1 2018-03-29T17:37:03Z localhost Survey123forArcGIS 26697 - [AppStudio@11205 category="qml" function="updateRelationships" filename="XFormFeatureService.qml" line="876"] qml: Updating relationship for: PlotChar <10>1 2018-03-29T17:37:03Z localhost Survey123forArcGIS 26697 - [AppStudio@11205 category="qml" function="updateChildRelationship" filename="XFormFeatureService.qml" line="810"] qml: Unsupported childKeyField type: esriFieldTypeString <15>1 2018-03-29T17:37:03Z localhost Survey123forArcGIS 26697 - [AppStudio@11205 category="qml" function="updateRelationships" filename="XFormFeatureService.qml" line="876"] qml: Updating relationship for: PlotObservation <10>1 2018-03-29T17:37:03Z localhost Survey123forArcGIS 26697 - [AppStudio@11205 category="qml" function="updateChildRelationship" filename="XFormFeatureService.qml" line="810"] qml: Unsupported childKeyField type: esriFieldTypeString <15>1 2018-03-29T17:37:03Z localhost Survey123forArcGIS 26697 - [AppStudio@11205 category="qml" function="updateRelationships" filename="XFormFeatureService.qml" line="876"] qml: Updating relationship for: Soil_Stability <10>1 2018-03-29T17:37:03Z localhost Survey123forArcGIS 26697 - [AppStudio@11205 category="qml" function="updateChildRelationship" filename="XFormFeatureService.qml" line="810"] qml: Unsupported childKeyField type: esriFieldTypeString <15>1 2018-03-29T17:37:03Z localhost Survey123forArcGIS 26697 - [AppStudio@11205 category="qml" function="updateRelationships" filename="XFormFeatureService.qml" line="876"] qml: Updating relationship for: SpeciesRichness <10>1 2018-03-29T17:37:03Z localhost Survey123forArcGIS 26697 - [AppStudio@11205 category="qml" function="updateChildRelationship" filename="XFormFeatureService.qml" line="810"] qml: Unsupported childKeyField type: esriFieldTypeString <15>1 2018-03-29T17:37:03Z localhost Survey123forArcGIS 26697 - [AppStudio@11205 category="qml" function="updateRelationships" filename="XFormFeatureService.qml" line="876"] qml: Updating relationship for: UnknownPlants <10>1 2018-03-29T17:37:03Z localhost Survey123forArcGIS 26697 - [AppStudio@11205 category="qml" function="updateChildRelationship" filename="XFormFeatureService.qml" line="810"] qml: Unsupported childKeyField type: esriFieldTypeString <15>1 2018-03-29T17:37:03Z localhost Survey123forArcGIS 26697 - [AppStudio@11205 category="qml" function="updateRelationships" filename="XFormFeatureService.qml" line="876"] qml: Updating relationship for: Lines <10>1 2018-03-29T17:37:03Z localhost Survey123forArcGIS 26697 - [AppStudio@11205 category="qml" function="updateChildRelationship" filename="XFormFeatureService.qml" line="810"] qml: Unsupported childKeyField type: esriFieldTypeString <15>1 2018-03-29T17:37:03Z localhost Survey123forArcGIS 26697 - [AppStudio@11205 category="qml" function="updateRelationships" filename="XFormFeatureService.qml" line="876"] qml: Updating relationship for: Routes <10>1 2018-03-29T17:37:03Z localhost Survey123forArcGIS 26697 - [AppStudio@11205 category="qml" function="updateChildRelationship" filename="XFormFeatureService.qml" line="810"] qml: Unsupported childKeyField type: esriFieldTypeString <15>1 2018-03-29T17:37:03Z localhost Survey123forArcGIS 26697 - [AppStudio@11205 category="qml" function="updateRelationships" filename="XFormFeatureService.qml" line="876"] qml: Updating relationship for: PlotCircle <10>1 2018-03-29T17:37:03Z localhost Survey123forArcGIS 26697 - [AppStudio@11205 category="qml" function="updateChildRelationship" filename="XFormFeatureService.qml" line="810"] qml: Unsupported childKeyField type: esriFieldTypeString <12>1 2018-03-29T17:37:03Z localhost Survey123forArcGIS 26697 - [AppStudio@11205 category="default" filename="XFormFeatureService.qml" line="876"] qrc:/qml/XForms/XFormFeatureService.qml:876: TypeError: Cannot read property 'name' of undefined <12>1 2018-03-29T17:37:57Z localhost Survey123forArcGIS 26697 - [AppStudio@11205 category="default"] QEGLPlatformContext: eglSwapBuffers failed: 300d <12>1 2018-03-29T17:37:57Z localhost Survey123forArcGIS 26697 - [AppStudio@11205 category="default"] QEGLPlatformContext: eglSwapBuffers failed: 300d <15>1 2018-03-29T17:37:57Z localhost Survey123forArcGIS 26697 - [AppStudio@11205 category="qml" function="expression for onStateChanged" filename="Portal.qml" line="192"] qml: Application state changed: 0 <15>1 2018-03-29T17:37:57Z localhost Survey123forArcGIS 26697 - [AppStudio@11205 category="qml" function="expression for onStateChanged" filename="Portal.qml" line="192"] qml: Application state changed: 0 <15>1 2018-03-29T17:37:59Z localhost Survey123forArcGIS 26697 - [AppStudio@11205 category="qml" function="expression for onStateChanged" filename="Portal.qml" line="192"] qml: Application state changed: 4 <15>1 2018-03-29T17:37:59Z localhost Survey123forArcGIS 26697 - [AppStudio@11205 category="qml" function="onRunningChanged" filename="Portal.qml" line="559"] qml: Token expiry timer disabled <15>1 2018-03-29T17:37:59Z localhost Survey123forArcGIS 26697 - [AppStudio@11205 category="qml" function="onRunningChanged" filename="Portal.qml" line="557"] qml: Token expiry timer will trigger in 27.4194 minutes <15>1 2018-03-29T17:37:59Z localhost Survey123forArcGIS 26697 - [AppStudio@11205 category="qml" function="reset" filename="Portal.qml" line="591"] qml: Reset token expiry timer: Thu Mar 29 12:06:24 2018 GMT-0600 minutes: 27.419433333333334 <12>1 2018-03-29T17:38:00Z localhost Survey123forArcGIS 26697 - [AppStudio@11205 category="default"] QEGLPlatformContext: eglSwapBuffers failed: 300d <15>1 2018-03-29T17:38:00Z localhost Survey123forArcGIS 26697 - [AppStudio@11205 category="qml" function="expression for onStateChanged" filename="Portal.qml" line="192"] qml: Application state changed: 0 <15>1 2018-03-29T17:38:00Z localhost Survey123forArcGIS 26697 - [AppStudio@11205 category="qml" function="expression for onStateChanged" filename="Portal.qml" line="192"] qml: Application state changed: 0 Thank you! ... View more

I just hit this bug today as well.  Funny thing in my form was working in my test service.  I republished it to a new service and suddenly it is hanging on Getting Service information.  It is hanging on a related table - that very last one in the list.  I didn't change anything on it. This also happened to me a few weeks ago when I had a photo in a repeat.  Got rid of that and it all worked. At a dead stop now.  I am working with the admins but does anyone know any thing else that could cause it?  It was working yesterday. Further testing shows it hangs on the last item in the HFS no matter what it is.  So it is not a specific form.  Note this is a HFS with a submission_url used.  If I publish the forms to their own spot they work. Edit:  Just looked it up and this bug is supposed to be fixed? BUG-000103217: This software defect caused the Survey123 field app to hang when attempting to submit data to a survey if the logged-in user had been revoked permissions to access the underlying survey’s feature layer. In version 2.2, the Survey123 field app will report a descriptive error message when this situation is encountered. Thanks ... View more