Latest Contributions by DerrickWestoby

This is a quick reply because I'm on my phone....but I'm wondering if I misinterpreted your question.  Are you just asking if you can geocode a polygon in S123 to store the address info in fields? If that was the question....no. but you could have a null geopoint in your survey and geocode that.    And if you want the link in the pop-up to pre-fill some survey123 questions via url parameters, no you do not need a common field to join them (for it to function, at least. Its a good idea just to have one available though).  If you want to use the link to launch a S123 form where you are editing the existing polygon feature (instead of creating a new feature), yes you would need to reference the objectid or globalid, along with enabling edit mode.  If you want the pop-up to be updated with whatever information you're putting into the survey123 form, you would not need to create a link/join field to see the info from s123 if you set it up to edit the existing polygons. That link would have been handled when you launch the s123 form to edit. If you want to view the submitted info in the polygon pop-up and the s123 form is set up to create new features with a common join field, then yes, you'll want that available (and globalId is a good idea).    ... View more

Yes I did.  I edited the resolution into my last post, but here it is as well.  (use "predictivetext multiline", NOT "multiline predictivetext") EDIT for posterity: This was confirmed as a bug (BUG-000146779), but using "predictivetext multiline" in the appearance column (instead of "multiline predictivetext") does work. While troubleshooting, we noticed that "multiline predictivetext" will work if it's present when the survey is first published, but not if it's changed after first publishing.  ... View more

(This is just some info to move you in the right direction.  I haven't used MS Flow and my workflows are normally the opposite of what you're doing)   "Multiple emails for each line in the repeat table" This is resolved by using an array aggregator to combine each bundle into one.  Sorry I don't have a screenshot to show you how it would be configured in Integromat. I do the opposite with an iterator, so that I can add each record as a row to a spreadsheet (which would cause an email to go out for each record, which is what you're seeing). On the off chance it helps to, here's a screenshot of how my iterator is set up by pointing at the repeat table:   Once you get all of your repeat records aggregated to a single bundle, it'll end up sending out a single email instead.    "Only email the last repeat section" I'm not sure if this means that you only want to email the aggregated repeat table (meaning every record in the repeat combined into a single bundle) or if you're saying that you want to find the very last record in the repeat and only email that one.   If you're after the latter....you can ignore the first part of my post since you won't need to aggregate all those records into one.   You would need to find the max() index of the record in your repeat and then set up MS flow to only email the record for that index position.  I'm not sure how this looks in MS Flow, but in Integromat you could insert that index position here: (Sorry if this post isn't much help - I spent a lot of time trying to figure out how to work with the repeats when I first set up integromat and I would have saved a lot of time if I'd know iterators and aggregators even existed.) ... View more

Try this instead: arcgis-survey123://?itemID=7f0e5eb93d424c1ea532da3d684c6a75?field:plot={st-cty-plt} The first URL parameter needs to be preceded by a ? Subsequent parameters should be preceded by a & ... View more

This happens fairly often due to issues on ESRI's site, in my experience.  Most recently, timed with the 3.14 release as others have said.     Other than that, I've seen the issue when my reports are generating maps with vector layers that fail to draw or are unavailable.  For instance, I used to use a basemap that contained a taxlot/parcel polygon layer that was hosted by the county in AGOL.  If they were doing maintenance to that layer, or if my map extent was very large and included a large amount of features, my feature report would timeout while trying to generate the report.   ... View more

If the polygon they are clicking on contains that information in the polygon's fields, yes you can accomplish this with Arcade & URL parameters.   (Here's a link to Ismael's blog post describing the process) 1. In your web map, select the polygon layer, "configure pop-ups", and then "manage expressions" 2. You'll see a window like this: Edit this Arcade Expression to suite your needs and save it: var urlLink = 'https://survey123.arcgis.com/share/SURVEY-ITEM-ID-HERE?field:FIELDNAME1=' + $feature.Field1 + '&field:FIELDNAME2=' + $feature.Field2 return urlLink (If you click "test" at the top of the screen, you can try it out and then copy and paste it into a new window to make sure you set it up correctly. ) 3. Use the Arcade Expression that you just setup & saved in your feature's popup:   *** If the address information you want to use is NOT stored in the polygon layer, I'm guessing you'd have to do something that's beyond my skills (and probably served by a custom Javascript web app or Experience Builder that might support something like geocoding by user click).  ... View more

Ahhhh, that looks like your "Create Feature Report" module wasn't set up correctly. Should be a quick fix:  Make sure you're drawing from the correct spot in the "Watch Webhook" module for that objectId, and also double check that your connection, survey and report template are correct.    ... View more

You need to share your survey with "everyone" in order to embed it, correct? (I think since v3.12?).  Does "keep  track of who created and last updated features" work with layers that are shared publicly?  Both of these have changed since the last time I looked at them (and I'm not an enterprise user), so I'm not sure how to resolve your issue but this is where I would start.   First screenshot is the Survey123 settings on the survey123 website. The second screenshot is the "settings" page of the hosted feature layer on AGOL.      ... View more

I had tried using html when I first tried this, but it didn't work for me. I'm guessing that's what she did as well? Something like: <a href = "${feature_URL}" target = "_self">Click here to be redirected</a> Would just print out something like this in the feature report: <a href = "https://tinyurl.com/2p89mxdb" target = "_self">Click here to be redirected</a>   ... View more

You have a polygon layer and you want to use Survey123 to update fields in that polygon layer, correct? (Not copy the geometry to a new layer, not create a related table with some sort of matching/join field?) If that's the case, you need to use the option to create a new survey123 form from an existing feature layer (This is in Survey123 Connect....I haven't used the web designer in over 3 years so not sure what options existing there now) In the example above, I'm using the "Feature Service" option to create a new survey from my "UAS Mapping Extents" feature layer.   A few random thoughts (based on ~2yr old experience with it): You cannot add new fields to this feature service by creating new fields in S123 connect and publishing, in the same way that you would have with a feature service created by S123 Connect.   I would recommend adding the fields that you're planning to use in Survey123 to the feature service ahead of time, either through the AGOL interface or ArcPro.   When you create a survey from an existing feature service, the XLS that's generated as your starting point can be a little....messy. In general, Don't touch the values in the "name" column, but you can update the "Label" column to something human-readable if it's not already.  Take the time to set the bind::esri:fieldType and bind::esri:fieldLength columns to an --exact-- match for the values in the hosted feature service (in my experience, these were never populated when creating a new survey from a feature service.  I've been waiting for the day that this changes) Make sure you set your survey up to support editing existing features and the query parameters, since all of your submissions will be editing existing features (I think this is all handled by the prompt you get when publishing your survey now, since the 3.13 release of Connect)   EDIT: I missed the last part of your question, which was how can you make sure you're adding data to existing polygons, not creating new ones.    What I posted above is still correct, but you'll need to set up a way for people to access and edit the existing polygons.  There's many ways to do this.   - Use the "inbox" in the Survey123 App to find an existing record and then open it for editing:   -Use a web map to generate dynamic links to edit the selected feature via Survey123 web form URL parameters (Via arcade expressions and the feature popup)(can also be utilized in field maps and collector): Arcade Expression used for that highlighted hyperlink above: var urlLink = 'https://survey123.arcgis.com/share/SURVEY-ITEM-ID?mode=edit&globalId=' + $feature.GlobalID + '&field:closeout=no' return urlLink -Using Ops dashboard and a list element + embedded element (similar to the approach above)   Embedded content element set up to show the embedded survey123 web form, with URL parameters to access a specific record (objectID) in edit mode (This is an old setup. You'll need to use globalID now) List element set up to filter the embedded content window to the objectID that's selected.         ... View more

Is the generated_note field within a repeat?  If so, that's a known bug/limitation.   You can't update an already-published survey with a NEW field inside of a repeat unless you are also adding a NEW field outside of the repeat.   Assuming that's what you're seeing.... Add a new field outside of the repeat called "delete_me" Add your generated_note_form_footer field inside of the repeat.  Publish, which will create 2x new fields.  After you publish, remove your "delete_me" field and publish again.   Once that's done, go to your feature layer in AGOL and delete the "delete_me" field from the feature layer.  ... View more

Wasn't there an issue that popped up with 3.13 as well, @Anonymous User ?  I thought I remember something changing with the allowUpdates=true and/or the query where clause changing the behavior of edit & resubmit or copy to new options, especially on surveys with repeats and image attachments?  ... View more

When you run the scenario, what does that module report?    Does the submitter's token have permissions to update features in that feature layer?    Edit: I wasn't going to post this because I know it's not set up correctly, but it's been working for the last 3 years so I haven't fiddled with it (this is the first time I got an update feature call to work in here, so I didn't change it once I got it working). Posting it anyways just in case it helps.    ... View more

I don't think you remembered incorrectly, @JohannesLindner ...I think this behavior changed within the last year.   ... View more

Using a JS script in-app like @HuubZwart recommended is probably the "cleanest" way to do this, but difficult.  An easier option, if the limitations are acceptable, would be to print them out in a feature report in a different spatial reference. I'm not sure what the WKID of GDA94 is, but you could replace 4326 with that and then print out your points in a table that could be easily copy and pasted into a CSV file to import elsewhere.  Feature Lat (4326) Lon (4326) Elevation (Meters) ${feature_number} ${location | getValue:"y":4326} ${location | getValue:"x":4326} ${location | getValue:"z"}         (I had some of my surveys set up this way before I figured out how to auto-export directly to a CSV) Relevant help doc - https://doc.arcgis.com/en/survey123/browser/analyze-results/featurereporttemplates.htm ... View more