Latest Contributions by Jim-Moore

Hi @TrevisMartin, could you please provide some screenshots (or if possible a screen recording) of the behaviour? Which version of the Survey123 field app are your personnel using? By menu bar, do you mean the iPhone's status bar, or the header of the survey form itself? Note that it's usual behaviour on iOS for the survey form to shift upwards to make room for the keyboard, if the keyboard would otherwise obscure the question (for example, if the question you're answering is towards the bottom of the screen). For questions near the top of the screen, the keyboard can safely 'float' over the lower part of the form without obscuring the question you're answering. Best, Jim ... View more

Thanks @PaulMillhouser, it was a long shot! If you're able to share your XLSForm that'd be great so I can attempt to troubleshoot. Feel free to send to me by direct message. ... View more

Hi @PaulMillhouser From your screenshot of the conversion error, it looks like there might be an erroneous space in the question type? Best, Jim ... View more

Hi @AustenPepper  When talking about supported languages, there's a distinction between the languages that the Survey123 UI supports (Connect, field app, and web app) and the languages that your survey's XLSForm can accept. As @IsmaelChivite mentions in this post, the language code is used to determine the app's UI language; when selecting a language, the app's interface (menus, options, etc.) will also switch to that language, if it's supported by Connect, field app, and web app - see the list of supported languages here. The XLSForm specification references this document as the list of languages supported in XLSForm, which appears to include three-character subtags. So for Tok P**in, you can use ::Tok P**in (tpi) as the suffix for your column headers (labels, hints, etc. as configured in your XLSForm) to translate the content in your survey form. Note that Tok P**in (tpi) is not a supported language for Survey123's UI, so while your translations will appear in the survey form when this language is selected, the app’s UI will not change (the app will remain in the default language). Also note that for the language name, you can actually use any string you like, so long as all columns containing this language use the same notation. For example, label::Spanish (es) would work the same as label::Español (es) - the only difference would be how the language name is displayed in the drop-down language selector. Hope this helps, good luck with your multi-language surveys! Jim ... View more

Hi @LindseyStone  Just to clarify, the XLSForm templates are updated with each release of Connect to ensure all of the supported question types, appearances, columns, etc. are in the template - however, the template version you're using doesn't matter; the Survey123 software version will determine if a feature is supported or not.  If you'd like to use the latest XLSForm template for your survey, you can copy and paste the content from the old XLSX file into a copy of the new one. Then replace the old XLSX file in the survey's folder with this new one (with same filename). It's recommended to use 'paste values' so that you do not disrupt the data validation. Please see the instructions/tips in the Migrate an existing survey to a new template section in this blog post for more details. Regarding creating a new feature layer: for a survey that's already published, some subsequent changes to the XLSForm (e.g. changing a question's type) will cause the feature layer to be rebuilt; other changes can be made while retaining the existing feature layer (e.g. modifying a calculation on a question). For more on this please refer to the Update surveys section of the documentation. Best, Jim ... View more

Hi @JeremiahJones  Would it be possible to attach a screenshot or two to demonstrate how the check mark is appearing on different platforms? If you could attach your XLSForm that would be great too (or at least the instance name it uses). It's likely that the way that character is rendered varies depending on the operating system; you could try changing the font in the Survey123 field app (under Settings > Text) to see if that changes how the symbol is displayed. Thanks, Jim ... View more

Hi @LindseyStone  To hide a group, enter 'hidden' in the appearance column on the begin group question. Any defaults or calculations on the questions inside the group will be retained. The XLSForm you provided is using an older version of the Survey123 template, so 'hidden' is not available in the drop-down for appearance; however, please note that the data validation for the various columns in the XLSForm template serves only as a guide (you can change this as required). The latest versions of the Advanced and Standard templates (available in Connect) include 'hidden' in the drop-down for appearance (this appearance was introduced in 3.11). Also note the 'autocomplete' appearance is for select_one questions and allows the user to start typing an entry into a text box, which then filters the list of choices as they type; it does not apply to dateTime questions or any other question type (and is of no use for hidden select_one questions). Hope this helps Best, Jim ... View more

Hi @LauraEDugan  Thanks for attaching your XLSForm. As you're seeing, if more than one choice is selected for the level II select_multiple, the regex() will return multiple matches. For example, if threat_invasive has answers 8.1 and 8.4, the value stored for this question is '33,142', so all choices matching 33 and 142 will be returned. You want to return the '33' choices only for one question, and the '142' choices only for another question, so I think in this case the solution is to use separate choice lists for each level III option. Because each choice list is discrete (i.e. the level III choices are unique/static for each level II choice) and displayed in its own question, there is no need to use a choice filter. You've already implemented relevant conditions to control which questions (and choices) the user sees. If you wanted to have only one question for level III and dynamically adjust the choices presented in it from a longer list if all potential level III choices, a choice filter would be necessary. I also noticed that the select_multiple questions have bind::esri:fieldType set to integer, which is incompatible with select_multiple questions as the answer to a select_multiple is stored as a comma-separated string (for example, '33,142'). Select_multiple questions use a string field in the feature layer by default. Note that if you want to save each selected response as an integer, you could consider using the technique described in this blog post to save out the selections to separate fields. See the Controlling how user selections are stored in ArcGIS section. Regarding the threat_agri_aqua question appearing in the form validation, is it possible that this choice was selected and then deselected? In that case the remnant entry might still be shown in the field list. In any case, the value is null so no data would be sent for this field on submit. Best, Jim ... View more

Hi again @LauraEDugan - forgot to mention that this blog post is another excellent resource: https://community.esri.com/t5/arcgis-survey123-blog/survey123-tricks-of-the-trade-choice-filters/ba-p/894046   ... View more

Hi @LauraEDugan  I think your theory is on the right track - the choice filter expression filter=${threat_invasive} is expecting one value, but the threat_invasive question is a select_multiple, so you'll likely need to use a different technique here. The Cascading Selects sample in Survey123 Connect has several examples on how to set up choice filters for select_multiple questions, including the use of regular expressions. Perhaps a regular expression like regex(${threat_invasive},filter) might work? Not sure about the  threat_agri_aqua question - if possible, could you please attach your XLSForm? Best, Jim ... View more

Hi @FedericoRiet_Sapriza  It sounds like you want to ignore from the count any zero values (where the user has input 0 on the range slider), is that right? The count() function counts all instances of a repeat question that contain a value (that includes 0). One option that might work is to omit the records where the value is zero using an if() statement. Please see attached example. Optionally, you could set the field type for the range questions to null to omit them from the feature layer to avoid duplicate data. One thing to note is that with this example, if the user enters 0 for the range question, it gets converted to a blank ''. If it's important to retain the zero, an alternative could be to make the second field in the repeat a counter, using something like if(${producto_1_1_1}>0,1,0) and then use sum() in the contar_respe field to get the total number of non-zero entries. Best, Jim ... View more