Latest Contributions by HannahFerrier

We try to update Survey123 for ArcGIS around the first day of every month. We made the Fools Day (April 1st), May Day (can you guess the month?), Children's day on June 1st, Tartan Day (July 1st) and of course, the International Beer Day on August 1st. Here we are in September 1st... So here is our update! In the Random Acts of Kindness update, we have put special emphasis in the Survey123 Connect component. In particular, we introduced fixes to go after the not so kind and not so random XLSForm Conversion Failed error. Turns out that some of you are running Survey123 Connect in networks configured with proxies and these were causing systematic errors every time Connect was attempting to validate your XLSForm. We want to say thanks to all of you giving precious information to narrow down the problem. With this update we think that proxy issues in Connect should now be addressed, but we will keep an eye on our public repo in case that you still run into problems. Unfortunately, we are unable to sign the Windows version of Survey123 Connect at this time, but as soon as it is possible, the installer will be updated. In the meantime, please ignore any 'unknown publisher' warnings during installation. Another big one coming with this update relates to Windows 10, which is now supported with Connect and the app. Finally, some of you were not able to create Surveys with special (non ASCII) characters in the name. This was especially problematic in some languages like Portuguese and Japanese where the default names suggested by Connect had special characters. Thanks again for reporting this issue... unless you tell us... we can't really fix it. You can always check the most up to date information about our road map  here. For those of you that are more closely following our road map, you will have noticed that we had plans to incorporate Cascaded Selects and Windows Phone 8 and 8.1 in this update. We are going to push these into the next milestone (October 1st).  Support for XLSForm Repeats continues to be planned for the October 1st update. As usual we will keep a close eye on your questions in GeoNet as well as any software defects and enhancement requests you log in our repo. We now will call this a day and figure what our random act of kindness will be. The Survey123 team. ... View more

Formulas supported in Survey123 include the following operators: Symbol Function Example + Addition 2 + 2 - Subtraction 2 - 2 * Multiplication 2 * 2 div Division 2 div 2 = Equal .=10 != Not equal .!=10 < Less than .<10 <= Less than or equal to .<=10 > Greater than .>10 >= Greater than or equal to .>=10 or or .=10 or .=20 and and .>10 and .<20 Formulas can be used in Survey123 when building your forms in the following columns: Constraint Adding a constraint to a survey question will restrict the accepted inputs for a response. This could include a specific range of numbers, combinations of letters and numbers or general pattern matching. In your spreadsheet, the constraint expression is entered into the constraint field and helpful text is entered into the constraint_message field. In the constraint expressions, the input for the question is always represented by a full stop. For example, the following formula can be used to restrict the input of an integer field to positive numbers only: .>=0 Regular expressions can also be used for pattern matching to constrain valid responses. This regular expression can constrain the input of a string field to a well-known email address format: regex(., '[A-Za-z0-9._%+-]+@[A-Za-z0-9.-]+\.[A-Za-z]{2,4}') See here for more information on regular expressions... See here for more information on using constraints... Relevant A question, or a sets of questions, can be hidden and revealed based on previous answers using relevant expressions. These expressions are entered into the relevant column and the answers to previous questions are always referred to as follows: ${field_name}. You can apply a relevant expression to a single question, or group questions together and set the relevant expression for the entire group. For example, this expression will reveal a question if the answer to the previous question is true: ${previous_question} = 'true' This example will hide questions if the answer to the previous question was greater than 100: ${previous_question} <= 100 This example combines multiple operators and questions: ${previous_question} + ${other_previous_question} <= 100 When using mathematical operators, be aware that sometimes you may need to cast values into numbers. In the previous examples we assumed that previous_question and other_previous_question where integers or decimals... but what if the question types were strings? Then you cast them as follows: int(${previous_question}) + int(${other_previous_question}) <= 100 See here for more information about using relevant clauses... Calculations Calculations are performed in the calculation field of a question. Calculations are often associated with calculate type of questions, but can also be applied to integer, text etc type of questions. The outcome of the calculation can be used to populate relevant or constraint expressions by referring to the field name of the calculate question. They can be used to hold values that do not need to be displayed on the form, but are included in the feature service. For example, you can create a question of type calculate and name it calc, then insert the following expression int its calculation column: ${question_1} + ${question_2} + ${question_3} And then use the result to set the relevance for the next question: ${calc} <= 100 See here for more information on calculations... ... View more