Latest Contributions by ClaireProctor

Unfortunately, Survey123 3.0 is built using AppStudio 3.1, so the template in AppStudio won't be updated until the official AppStudio 3.1 release at the earliest. ... View more

I'm not sure what caused that error, but it probably wasn't the conditional statement. It looks like it might have just stalled at 'Printing', which is the first of about five steps. Error messages appear if a survey actually fails and a 'More Details' link appears in the box. The best I can suggest is just to retry and see if it happens again. I'm not sure if this is a known issue with the new printing setup or not. cc: Zhifang Wang ... View more

This also isn't currently possible to my knowledge, unfortunately; that used to be the functionality of geopoint questions in the web app, but there's not currently a way to restore it. I'll also raise that to the website team, though, I'm not sure if this is something we actually can't support, or just something that we don't currently support. ... View more

The example I gave should do the job, since we are still talking about a field in your feature service. Essentially, rather than actually display the value in the field, it shows and hides text based on what the value is. Just replace the field name 'priority' (I just guessed what the context of the question was there) with your field's name, and it should work. ... View more

Hi Anu, Customized report templates don't support HTML formatting (in fact, it's news to me that the default template does), so that's why your results aren't being formatted in the same way. Version 3.0 did introduce conditional statements, though, which should let you replicate the formatting in your report template. You can find the formatting to do this in the documentation: Print survey results—Survey123 for ArcGIS | ArcGIS  In your case, although I don't know your actual survey setup, something like this would list the 'Low' result as you have it in your survey (know that in most cases, select ones will be looking for the choice's label rather than the choice's name): ${if priority==”<font color='green'><b> Low </b> </font>”}Low${/} Repeat similar for all of your other results. You'll probably need to experiment to get the functionality and formatting that you want. ... View more

Unfortunately, functionality has recently changed so that questions that didn't display due to not being called as relevant now don't record values. This changed for the field app in 3.0, but may have been true before then in the website, I'm not certain. I will raise this with the website team, though. What I can suggest is that you experiment with setting the geopoint question to read-only through Survey123 Connect and then loading it in the website; while users will be able to see it, they won't be able to write values to it. I will warn that I couldn't get this to work in my case, though. ... View more

This is likely two different issues. We do have as a known issue on Android that, if the app is closed, it doesn't retain the user's login information on being reopened. This is an issue specific to Android, and hasn't been observed on other platforms. We haven't seen an issue on being signed out after an amount of time has elapsed. I'm currently testing this on both Android and iOS. Can you confirm if one or both of these behaviors have appeared on both Android and iOS? ... View more

Hi Kevin, This is on purpose, and has been for a while; the field length of an integer value is by default capped at 9, because the maximum possible 32-bit integer value is ten characters (specifically 2,147,483,647). You can extend the length of the integer field by entering a larger number in the bind::esri:fieldLength column of your spreadsheet for that question, but entering a number higher than that maximum integer value will cause an error. What I would suggest in your case, with phone numbers, is that you instead use a text field. Your phone numbers don't need to be stored as integer values, because you don't need to treat them as numbers in calculations. You should then limit the input to that field to numbers using an input mask, which can also be used to provide some standard formatting to make the phone number easier to read. We provide an example mask specifically for United States phone numbers in our documentation on input masks: Esri custom columns—Survey123 for ArcGIS | ArcGIS  ... View more

Hi Joe, If you don't include a geopoint question in your survey, the field app will still capture a coordinate behind the scenes. This doesn't work for the Survey123 website, however, which only captures a location if a geopoint question is in your survey. ... View more

Hi Ryan, This makes things a bit messier; we haven't seen the same issue on iOS. Can I confirm that your workflow is the same as what Will described in the original post (sign in on both apps > open URL to Survey in Collector > complete survey > get asked to sign in again)? ... View more

In that case, yes, this does appear to be a known bug introduced in version 3.0, that's likely related to a new method of storing user credentials. We're hoping to solve this in version 3.1. ... View more

Hi Will, Can I ask what operating system you're using? We've seen a bug like this on Android devices. ... View more

Hi Erinn, This is a bit of a tough one for me, because I'm not tremendously familiar with Map Viewer, so you might want to look around further since I'm basically just making an educated guess. But from what I can gather, you might be able to alter the output of attributes by digging into the IdentifyFeaturesView object in the PanelPage.qml file. ... View more