Latest Contributions by AliciaRitzenthaler

No luck with 'and' either unfortunately. ... View more

Can or/and statements be used in constraint statements too?  I have the survey questions 'Select the most abundant', 'Select the 2nd most abundant', and 'Select the 3rd most abundant'. I'd like to constrain the response to the 2nd and 3rd most abundant questions so that users cannot choose a response they selected for the previous question.  .!=${mostabundant} seems to prevent the 2nd most abundant response from being the same as the most abundant answer. .!=${mostabundant} or .!=${2ndabundant} however does not achieve the desired response; the 3rd most abundant can be the same as either the most or 2nd most abundant answer.  ... View more

Closely related to the original question, I am trying to pass the GlobalID from Collector features into a Survey123 field called CollectorID.  When the CollectorID field is text this works. When the CollectorID field type is GUID however it appears to work (GlobalD passed, no brackets) but I cannot save the survey. I get the following message: Any idea how to pass a GlobalID from Collector to a GUID field in Survey123? I am passing the GlobalID to a GUID field because I need to set up a relationship class between the Survey123 and the Collector features based on this passed GlobalID. If someone has an alternative way to get around this I'm also open to that. ... View more

ichivite-esristaff‌, JTedrick-esristaff‌, dougbrowning‌ I pass the GlobalID of the Collector feature to an attribute called CollectorID in the Survey123 feature class. When this CollectorID is set as a text field I could not seem to set up the relationship class. CollectorID is not a valid option even though the field exists.  When this CollectorID is set as a GUID field type I can create the relationship class. When the CollectorID is set as a GUID field type however, I cannot seem to save my survey anymore. I get the error message below.  Anyone have ideas?  ... View more

The Survey123 fc is populating after each survey 123 form is completed so I think that's okay. Must be something with how I set up the relationship class. Did you attribute your class in order to view the related records? ... View more

Doug Browning‌, this is great! Thank for you sharing.  I follow your flow and I think this will work for our purposes as well. That said, I'm having rookie trouble setting up the relationship class correctly. It's either that or the submission_url to the new HFS. Can you elaborate and/or point me to any additional resources which were helpful to you setting your program up? Once I've added some collector points and completed the linked Survey 123 form my relationship table is empty. If I open the attribute table of either the collector points or the survey fc the "collector2survey" column (name of the relationship class) is filled with (0) in every row. If I select a Collector point, and click the "show related records" link in the pop-up I get a message that no results are found. I'm finding the URL of the HFS I'm using as the submission url near the bottom of the HFS overview page. Does that seem right or is there another URL? It looks something like https://services1.arcgis.com/8eq00iyMv7Ls2xme/arcgis/rest/services/HFSname/FeatureServer Thanks! ... View more

Ismael Chivite, James Tedrick Jeff Shaner, Brent Pierce, and other Survey 123/Collector users: Our goal is to use Collector to place new features and Survey 123 to populate the attributes of those new features. Currently I have things set up so that once a new feature is created, the pop-up will link to the associated Survey 123 form. The FID of the Collector feature is passed to the form in order to create a unique key between features and forms. After the fact, as a post processing step, survey 123 table is then joined to the Collector features based upon that unique key. This works but is clunky. You've got a map full of near-duplicate features which can be somewhat confusing and essential post-processing. Is there a way to push back attributes to the Collector features from the Survey 123 forms? That would make our process far smoother. Can the collector-integration on GitHub somehow be used to achieve this? Reasons to not complete this data collection within only Survey 123 using geopoints: - Constrained to point features - Inability to leverage interactive basemaps allowing reference layer attributes to be viewed - New features do not appear on map in real time - Inability to collect features at a location other than that of your current GPS location Reasons to not complete this data collection within only Collector: - Extensive set of attributes (100+) being collected many of which are only relevant based upon responses to other attributes. The conditional programming possible in Survey 123 is far superior for ensuring accurate and complete data collection for this purpose than replying on geodatabase domains alone. ... View more

It's been a couple of years now since this was first posted. Has anyone found a way to do this yet? I am also very interested in auto-populating lat/long fields when I drop a point in Collector. Alternatively, can anyone suggest resources for where to start if I were to do this with some custom development? Ultimately I want to populate the lat/long in Collector so that I can pass these attributes to Survey123. ... View more

I am trying to write a custom URL to pass Lat/Long from Collector to populate Lat and Long fields in a Survey123 form.  I'm trying to interpret the following note from the original post above: If you want to pass lat/lon values from attributes in your feature, please be aware that the default formatting rules for the double data type cut-off decimal values to two. You will want to eliminate the formatting rule to pass all decimal values to Survey123. If you want to pass lat/lon values from the geometry in a feature use Geometry($feature).x and Geometry($feature).y Two questions: 1) Where/how to I eliminate the formatting rule to pass all decimal values to Survey 123?  2) Can someone provide an example of how to write the actual url scheme segment with Geometry($feature).x and Geometry($feature).y? I have tried the following but get the unsuccessful attached result. Note that StreamReachPts is the name of the geodatabase feature class which prompts this survey. &field:Latitude=Geometry($StreamReachPts).y&field:Longitude=Geometry($StreamReachPts).x Alternative ways to pass Lat/Long from Collector to Survey123 are also welcome. Thanks! ... View more

We hoped to try to use allow/don't allow nulls to essentially allow us to conditionally require fields while collecting data in the field using Collector for GIS (see reply to Micah Bibinski above). ... View more

We are actually setting up this feature class to be the editable layer in a Collector for GIS application. The hope was that we could require/not require fields when certain conditions were met (by allowing or not allowing null values) to enhance data verification/validation efforts during field collection especially since there does not seem to be a way to enable/disable fields conditional (or at all for that matter).  Survey123 is a most excellent tool for accomplishing these specific goals but unfortunately doesn't offer the interactive mapping we also desire. If only there was a way to fuse the two platforms... ... View more

Thanks! Success!  Also see related question which I didn't find until after I posed: https://community.esri.com/thread/192645-is-there-any-way-to-use-my-own-basemaps-in-survey123  ... View more