Latest Contributions by Katie_Clark

Hi Kylie! I would recommend looking into custom URL's: https://support.esri.com/en/technical-article/000017982 ... View more

Hi Ben, I'm not familiar with a way to generate this automatically with the summary report, but one thing you could do is add an integer field/column to the feature layer and generate the numbers through a field calculation before generating your reports.  This support article on How To: Sort and create a sequentially ordered ID field in an attribute table in ArcGIS Pro might help to get you started.  ... View more

Hmmm, I could be wrong about the jr-choice-name thing. At this point, since I'm not able to replicate the issue, you may want to open a support case with Esri Support so they can screenshare with you and better identify the problem. Good luck! 🙂 ... View more

That is very strange, if you're getting different results running the exact same survey XLS form on the same version of S123 Connect. Maybe try experimenting with removing the jr-choice-name and see if it works? Another suggestion would just be to try building a brand new survey using the same schema, sometimes that helps to reset things or at least test to see if it behaves differently in a new survey. Also, totally makes sense about the date field! ... View more

Ok, so I downloaded the attached version of the Survey and CSV, and set it up on my machine with Survey123 Connect v. 3.12.232. It seems to be working fine for me: when I choose values from the dropdown, the role auto-populates with the text in blue:   If I manually change the role after that, the text changes to black (which implies it should still be a value that the survey will accept). Do you experience different results when you test the survey in Connect on your machine? --- Also, unrelated to your initial post but I have some (admittedly unsolicited) feedback for the user-interface of your survey, since you said you were so new to it. I would recommend having the date question have a default value of today() or now(). Just one less "click" for the field worker to have to do! (They could easily still change the date if needed).     ... View more

Maybe I'm a bit confused, but I'm not able to reproduce the error you're showing. The "select their role" field populates with a string like "Test 18" based on the concatenation from previous fields. Do I need to do something different to try to replicate exactly what you're getting?  There may be something related to labels vs. names here?   Also, you've probably already referenced this, but just in case, this is a fantastic post about pulldata from James Tedrick.  ... View more

First question....is the CSV file stored in the "media" folder of the survey directory? ... View more

Are you referring to the question types of an existing survey? (i.e. changing a text field to select_multiple) If so, you can only achieve that by republishing the survey, and doing so will unfortunately cause you to lose any existing records that have already been collected. See the "Update Surveys" section of this documentation to see what you can and can't change in a survey in order to preserve already collected data. ... View more

This seems to me like it good be a good scenario for using the pulldata function? You could have them select their name from the dropdown, and then populate their ID into a new field that would either be a "note" type, or hidden. You could even assign bind::esri:FieldType to Null for the name dropdown so it wouldn't become a field in the schema, if for some reason you only wanted to record the ID.   ... View more

Wonderful, glad it's working now! 🙂 ... View more

Hmmm, I've done this many times in surveys myself and haven't had an issue. What version of Survey123 Connect are you authoring this survey with? Also, I think having it in the default cell without quotes should be correct, but have you tried putting it in quotes to see if that changes it? Also, what appearance do you have for each of the select_one questions? ... View more

That's very interesting to hear your feedback! With this particular form, I actually created a python script first to do the calculations on the feature layer, but that would have to be done in post-processing. The field crew said they either wanted things calculated and displayed "on the fly", or it wouldn't be much use to them and they would proceed with purchasing a software service that does something almost identical. I was hoping to be able to save my company a lot of money by just using Survey123 which we already have.  I'm just starting to look into the EAC 3.14 version. On Android, the survey opened in only 10 seconds compared to 2.5 minutes, so that's promising! ... View more