Latest Contributions by Katie_Clark

Thanks Ismael! I know these bugs are frustrating for everyone, but we appreciate your hard work! ... View more

This is a really interesting question, I too would like to hear what other people have found to work best for them. Personally, I usually use underscores in the list_name if it needs to be more than one word, which is just a habit based on my departments convention. As for Name vs. Label, it depends on if the list will be used in a select_one or select_multiple question. If it's for a select_one question, I usually make the Name and Label identical, so I don't have to worry about which version will appear in the tabular version of the data. I haven't had any issues with special characters, it seems to accept the same format. If it's for select_multiple, then I use underscores in the name since it won't allow spaces. Also, maybe it's a holdover from other programming courses I've taken, but I almost always use lowercase letters in my coded values (list_name, name, etc).   There are also times where the Label needs to be an entire sentence or two based on the form I'm constructing. My approach for the name varies depending on how I need the answer formatted. Sometimes, the Label will be an entire sentence but the Name is only a number. I can then use this number in calculations elsewhere in the form, since it's used as an overall score for that metric. (i.e. If the user selects the option "Less than 10% of the bottom covered by excessive sediment deposition; bars with established vegetation.", assign a score of 5.) If I don't need to use the value in a calculation and I have many different choices, sometimes I just use acronyms and numbers. (i.e. I have a "Prescribed Burn Checklist" question in my survey, with 12 different values. The Label will usually be pretty long, but the Name will just be something like pb1, pb2, etc.) Anyway, that's my approach. 🙂   ... View more

@IsmaelChivite @JamesTedrick  Seems like this is a pretty widespread issue - any chance the Survey123 team will be able to look into this? ... View more

@jcarlson explained it perfectly. I just wanted to add on that you might want to set the value in the bind::esri:fieldType column in the XLS form to null for those "report" questions in the form. This is helpful when questions need to be used in the survey for calculations or to help with UI, but you don't want/need them in the final schema of the feature layer. Hope that helps! ... View more

I just had the same thing happen to me!  Katherine_Clark_0-1648058222052.png   I also recently upgraded to 3.14.   ... View more

What User Type/Role does the user have that is trying to make the edits? ... View more

Thanks Ismael. I updated my version of Connect to the latest version (3.14) and the grids appear to be working. Not sure why it would have stopped working in a previous version though, because it used to work... I admit I was a bit "scared" to upgrade, as I've heard about so many issues after upgrading to 3.14. But, fingers crossed things will be fine since it's been a while now since the new version release.  Thanks! ... View more

Happy to hear you found a workaround!  ... View more

I know I'm no authority on this, but as far as I know, Survey123 is still planned on being kept separate. My guess is just that rumors stick around a lot longer than they should?  Obviously I'm in the same boat as you, where I'd love to know if this isn't the case! ... View more

Would you be able to share your XLS form?  ... View more

I feel like this is a very common requirement and should definitely be included as a functionality when using the page style. I too am surprised it hasn't gained more traction! ... View more