Latest Contributions by JamesTedrick

As indicated in the comments, this is a supported workflow for Survey123 ... View more

@Katrin,   Can you provide more details on the file types you mention?  Survey123 is limited to the allowed file types; refer to the "Supported attachment formats" from this page in the ArcGIS Online documentation. ... View more

To note, custom JavaScript functions (which would allow for the text parsing described) were released in the 3.10 release ... View more

A quick update to this - the 'geocode' is now in beta on the Survey123 website.  Please refer to this document in the Early Adopter Community for more information. ... View more

Hi @DelaereMickael , We have released the Feature Report REST API through the ArcGIS for Developer's site; you can read through it at https://developers.arcgis.com/survey123/api-reference/rest/report/ .  This is as close as possible to meet this requirement; with this, a user could click a link and start the process of generating a report.  Because generating a report could take up to several minutes, it isn't possible have the link directly provide the report.  Through the REST API, you can integrate report generation in your own web applications. ... View more

Hi @TonyDaSilva1 @E_-_MarieCook__GISS_ @GianniCampanile2 ,   Apologies for the delay in responding to this. With 3.12, there was a change in how lists are managed internally.  One of the changes addressed a set of BUGs that had been registered regarding the processing of choices with numeric values (for instance, numeric values being used in cascading selects); to address this, choice values are now being converted into a numeric type if possible.  While we had this change in the Early Adopter Community for a number of months without issue, we are receiving reports in situations like you describe, where the values are number-like strings that have leading zeros.  There are a couple of workarounds that can be used to ensure proper processing: If the number has at most 1 leading zero and a known length, it generally is feasible to have a subsequent calculation that prepends the zero by comparing the string-length value; for example, if an example value is 05678 (five digits with a leading zero), the function if(string-length(${q}) < 5, concat(‘0’,${q}),${q}) can be used to add the zero back to the string The choices could be altered to be processed as a string by prepending a character (such as ‘_’) and then a subsequent calculation removes the character: substr(${q},1) Both of these workarounds uses a second, calculate question to process the value in the form; this can be used in combination with setting the select_one/select_multiple's bind:esri:fieldType to null so that the intermediate value is not stored.  Given the feedback, we are investigating ways that the type of value in a choice list can be better specified and hope to improve this.   ... View more

@Marie-LouLabuschagne  1) Yes, the lists need to be reprocessed with every save.  We are looking into checking whether the time a choice list was last saved can be used to prevent this for some lists (external CSV files).  Would you be willing to share your survey so that we could understand why it is taking so long (feel free to email me directly at jtedrick AT esri.com) 2) I'm surprised that you reported this would work when not all questions were filled in before - the design of Survey123 is that empty questions have a 'NaN' value that prevents operation.  If you have questions that may not be answered, you should use the coalesce() function to provide a default value (0, in this situation) ... View more

Hi @Anonymous User  @jcarlson's solutions are very good.  I might suggest 1 small tweak: You should only need less than/less than or equal comparaisons for the first (16 if statements) solution; you can account for the wrap (large values being the same as smaller ones) by using the same value as the final 'if false' value.  As an example for the 4 directions (the splits at 45 degrees):   if(${bearing} <= 45, 'N', if(${bearing} <= 135, 'E', if(${bearing} <= 225, 'S', if(${bearing} <= 315, 'W','N') ) ) )     ... View more

Hi @BamJam , Can you provide a sample of the form and lookup you are using?  you can e-mail me directly at jtedrick AT esri.com ... View more

Hi @KerryKang , Without seeing your form design fully, it is hard to understand if there are any unintentional uses of the ArcGIS Online World Geocoder.  Is your testing using the Survey123 Connect, the field app or the web app? ... View more

@JoseBarrios1, This appears to be a duplicate post to https://community.esri.com/t5/arcgis-survey123-videos/need-help-with-survey123-inside-experience-builder/m-p/1030344#M13 - I've answered in that post. ... View more

Hi @JoseBarrios1 , As this concerns The Survey123 Widget in Experience Builder, this should be addressed in the Experience Builder community.  That being said, what you are seeing is the current design of the Experience Builder Widget - it supports the collection of new data only.  You can use the Embed widget in the same fashion that @JamieLambert mentions configuring Survey123 in a dashboard. ... View more

Hi @GrantBenn1 , Survey123 uses the export capability built in to ArcGIS Online, which does not have the ability to choose between field names or aliases at this time. ... View more