Latest Contributions by DerrickWestoby

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

I'm not sure I fully understand your question, but I'll try answering based on my understanding of it.  You're just saying that "Submitted" has become "submitted" and "Reviewed" has become "reviewed", correct?  A critical part to understand here is that your S123 options that draw from a list (domain) like this have a name/code value and a human-readable "label" value.      For instance, a Label of "Bald Eagle" might have a name/code like "bald_eagle".  Another thing to know is that the name/code and label values work as expected when you FIRST publish a survey, but if you updated the options in  your choice list at a later date, the labels are not copied over and you have to update these manually.  Here's an example.  This is the list, or domain, for my "Component" question, which I'm viewing in the AGOL feature layer data-> fields page for the component question.   All of the list options here are created from my list that's stored in the Survey123 XLS when I first published it.  The "Pipe" option, however, was added to the list after initial publishing and the "Label" was not copied over for this reason.  If I displayed this in a web map or printed out these options in a Survey123 feature report, the "Label" column is going to be what's displayed and "pipe" is the only one that wouldn't be capitalized because of what you're seeing here.  Assuming this is the issue you're trying to resolve, fix it by manually fixing the "Label" value in your Feature Layer's Data page by editing the list for that specific question.    Aside from that, I'm guessing that you may now have a feature layer with a mishmash of values that should be the same?  IE:  Features that should be marked as "Reviewed" might be "Reviewed" or "reviewed", resulting in a legend with 4x classes instead of two?  If that's the case, you could fix it with "Calculate Field", using Arcade, also from the feature layer's data page.   That is doable, but maybe a little more complicated if you haven't used Arcade much.  You could just manually correct each feature after updating your list option, if you have a small amount of features.   If you still need to use Arcade to fix this issue, just reply here and we should be able to get it sorted out for you.  I don't want to type out a long response to that if it's not an issue you're facing anyways.  Here's a quick example though:     ... View more

This is for the feature report itself, not the XLS form, right?  I believe that you need to use the NAME of your list choice, not the LABEL (but try both because I don't remember for sure)  ${if RecreationSpaces | selected:"fully_met"}${RecreationSpaces} ${/} ${if RecreationSpaces | selected:"not_met"}${RecreationSpaces} ${/} Notice that I'm just changing the font color of the call to print out  your ${RecreationSpaces} value.  You can do this in  your feature report as well.  Background color, highlighting, text color ect will work this way (and I believe it's only the $ symbol you actually need to change) edit: If you created your survey in the web designer, it may not be obvious to you that you have a name and label for your list options (or "Label" and "Code" when viewing in your AGOL Feature Layer details).  Here's a few screenshots on where to find that, assuming you don't see your name/code values otherwise (note that in my example, the name and the code match exactly. I try to do this on purpose, but it's usually not going to be the case)       ... View more

Hi SWilander,  I posted a response to your other question on this topic here - https://community.esri.com/t5/arcgis-survey123-questions/bundle-validation-error-survey123-and-integromat/m-p/1149313#M40930 It looks like your problem is a sneaky pipe ( | ) character, based on the screenshots in your post linked above.  If that's not the case, reply in the post linked above and we'll get it figured out.  (Posting here in case anyone else stumbles upon your question) ... View more

No, this is not possible right now.  I've mentioned it a few times in the Early Adopter Community and I could swear I submitted the idea in 2020, but I can't find it in a search.  ... View more

FYI - Your post/question was duplicated.  I posted a response in  your other post here - https://community.esri.com/t5/arcgis-survey123-questions/bundle-validation-error-survey123-and-integromat/m-p/1149686/highlight/true#M40960 ... View more

It looks to me like you have a pipe character ( | ) just before your URL in the "Get a File" module.  Try removing that.   I think that's your issue, but if it's not....make sure that your report was actually successfully generated by the "create a report" module.  After you run it, click in the "1" bubble above the module and expand the result files group to make sure a URL is actually being provided.  ... View more

You're welcome!  Get in the habit of searching for @IsmaelChivite 's Survey123 blog posts as well.  Assuming he's made one for the thing you're trying to accomplish, I find them a lot more helpful than some of the help docs.   Good luck!  ... View more

Agree with @HuubZwart  The approach I'd take (mainly because I prefer to use S123 Connect to create feature layers with a relationship): - Use the schema of your polygon layer to create a survey123 form (even if you don't want all the fields in the survey),  then use a repeat to collect your plant points and attributes.  -Publish to AGOL from Connect -Use the Append tool in ArcPro to append your existing polygons to the just-created (and empty) feature service -Add a field to your polygon layer, something along the lines of complete yes/no -In S123 Connect, create a NEW survey and select the option to create from an existing feature service, pointing at the service you just created and appended to.  -Remove all of the unwanted fields from layer 0 / polygon layer from your S123 XLS (they won't be removed from the feature service, just the form).  Up to you on how you want to mark a polygon as completed, but it could be a user-selection or auto-complete if you have >0 entries in your repeat or something.  -Make sure to enable edits and set up the queries that support editing from the inbox.    -Publish.  User's should be able to select a polygon from their inbox in the Survey123 form (the 2nd one you created from the existing feature service), or you could use URL parameters to launch it from a web map/collector map.  ***I'm sure there's a better way to go about this, but this is the approach I'd take on my first go because of frustrations with related labels, ParentGlobalID fields, etc and trying to use them in apps and dashboards later.    ... View more

I just checked a handful of my generated reports and it looks like the same on my end (with docx outputs, not pdf).  Prior to feb 2022, word documents were 2mb-5.5mb.   The 4x that I checked from this week were 9mb-12mb.  All include a repeat with photo attachments, usually 5x-20x photos.  ... View more

Something is failing in your scenario and you're packaging up the entire response as a file (pdf or docx) because you probably have something like [generated_report].docx as the attachment name.  View the history of your integromat scenario to figure out the error message and resolve that.  Once the report is being generated by the report module, use "HTTP GET - Get a file" module to grab the report via the URL, then attach that to your email.    ... View more

I was under the impression that all reports use credits, even if you're using the default/auto generated template. I've never actually looked into that, but I don't imagine that ESRI would charge for custom report templates but not the default one.   The "Preview sample report" option does not use credits though.    ... View more