Latest Contributions by Jim-Moore

‎02-14-2022

Hi @NathanialWigington Thanks for including your XLSForm. The selected() function you've used for the choice filters relies on the choice name (i.e. the value of the choice), not the choice label. Looking at the feature layer, it looks like UNITNAME corresponds to the labels in your Park_Name choice list, whereas ENTITYID looks like it corresponds to the choice names. Changing the pulldata() for the Park_Name question to reference attribute.ENTITYID instead should help. For MGTUNTIID, in the feature layer many of the values have a mix of upper- and lowercase letters, whereas in you choice list (and the MU column for the choice filter) they are all uppercase. Note that the choice names are case sensitive; so changing these to match exactly what's in the MGTUNTIID field should fix the Work_Order question. Hope this helps. Best, Jim

‎02-07-2022

Hi @LouiseHarris1 if you're using an older version of the XLSForm template, you can simply add a guidance_hint column to the survey sheet. Otherwise, you can download the latest versions of the Advanced and Standard templates from Connect (New survey dialog) and migrate your survey to the new template. You'll find some hints and best practices in this blog post - see the Migrate an existing survey to a new template section. Note guidance hints are supported in Survey123 version 3.12 and later.

‎02-01-2022

Hi @DerrickWestoby Thanks for raising this. For the forthcoming 3.14 release of Survey123, the behaviour for annotate questions has been modified so that if you have more than one method specified in body::esri:style (e.g. method=camera,browse,map) you'll be presented with a pop-up when you first open the canvas that allows you to choose the desired method. For reference, this is logged as ENH-000144493. If you only have one method specified, that method will be launched when the canvas is opened. If you don't specify a method, it will default to launching the camera when the canvas is opened. If you have a default background image set, this will also appear in the pop-up as an option. Please see the Using capture methods with the annotate appearance documentation on EAC. This functionality is also available for testing in the latest beta builds. Best, Jim

‎01-30-2022

Hi @JunFUKUDA Thanks for reporting this issue - there is a known issue in the Survey123 web app with URLs that contain curly brackets { }. This issue has been observed in the survey form itself, as well as the thank you screen. The Survey123 team is working on a resolution to this issue but no indicative timeframe at this stage. Please keep an eye out on the Survey123 blog and Early Adopter Community for release announcements. I would also encourage you to submit this issue to Esri Support so that it can be assigned a BUG number; this will allow you to track its progress. Best, Jim

‎01-30-2022

Hi @bhariadi Thanks for providing your XLSForm. Please see attached a simplified XLSForm that attempts to solve your problem using the count() function, and also by rearranging the questions slightly. One thing to note here is that I've avoided using aggregate functions (sum, count, etc.) inside the repeat that the function is aggregating. Please see the Survey123 Tricks of the Trade: Repeats blog post for some great info, as well as the documentation on repeats. Hope this useful, please let me know if this works for you. Best, Jim

‎01-30-2022

Hi @LouiseHarris1 A couple of ideas that might be of use: If you're authoring your survey in Survey123 Connect, one option would be to use a guidance hint. Guidance hints appear under the question label, either as a 'lightbulb' icon in the Survey123 field app, or an expandable panel in the web app. See the documentation on hints for more details. Alternatively, you could use a note question inside a group that uses the compact appearance (collapsed by default) - users could expand the group if they need to read the notes. Hope this helps. Best, Jim

‎01-19-2022

Hi @DarraghOSullivan Yes, you can use a question value in an expression filter for a map question (and most other question's expressions too!). The syntax in your example looks good. What issues are you encountering? Does the report fail to generate (and if so, is there an error message)? If the report does print, is the map missing? Is the question a geopoint, geotrace, or geoshape? Best, Jim cc: @ZhifangWang

‎01-19-2022

Hi @JavierCMartínezPrieto Are your entry and exit times entered using the time question type? If so, you can use something like the following to get the duration in minutes: (decimal-time(${exit_time}) - decimal-time(${entry_time})) *24 *60 Note that both time questions are in the same 24-hour period, so for example, if you enter 10:00pm for the entry and 2:00am for the exit, the calculation will result in -1200 minutes (i.e. back in time 20 hours). If you want your entry and exit times to cross from one day into the next, you could add the date to the value. One way to achieve this would be to use the dateTime question type instead for entry and exit, then use a calculation like: (decimal-date-time(${exit_datetime}) - decimal-date-time(${entry_datetime})) *24 *60 If you prefer to use the time question type, one option could be to add 24 hours to the exit time, if that time is less than the entry time. Expression could be something like: if(${exit_time} > ${entry_time}, (decimal-time(${exit_time}) - decimal-time(${entry_time})) *24 * 60, ((decimal-time(${exit_time}) - decimal-time(${entry_time})) *24 * 60) + 1440) One issue with this method is you would be relying on the user to enter the times correctly and making the assumption that they understand they're entering a time for the following day. It also wouldn't account for an exit time that was more than one day in the future (must be in the next 24 hours only). For this reason, the dateTime option is perhaps more reliable. Note these examples are in minutes but you could drop the *60 to get hours, but you might need to use the round() function to get a suitable result. For more help, see the Dates and Times sample XLSForm in Survey123 Connect, and check out the Dates and Time in Survey123 blog post. Hope this helps, Best, Jim

‎01-19-2022

Hi @JoyChen1 I have a couple of questions to help us troubleshoot your issue. Just to clarify, are you trying to view or edit previously submitted survey responses in the web app (using mode=view or mode=edit URL parameters) or are you trying to view survey responses in the Data tab on the Survey123 website? And just to check, your survey contains image questions and you're able to submit images without issue in the field app, is that right? Also when you say "updating the setting for the layer on the Web" what are you referring to? Thanks & best, Jim

‎01-11-2022

Hi @UğurBaranSarıbaş Thanks for the additional information, that makes sense. Just to double-check, is your URL using quotation marks, as shown above? If I publish your sample XLSForm and then open it in the web app using the following URL (i.e. without quotes) the choice list in the repeat works as expected: https://survey123.arcgis.com/share/39dd7973364041c6a3954024616e91c6?field:form=1 However, if I add quotes (i.e. form="1") it does not, which is expected as the quotes won't work in a URL. Please let me know if that might solve the issue. Best, Jim

‎01-09-2022

Hi @CurtisDeVault In the selected-at() function, choice_index must be an integer. From the same documentation, the selected-at() function "returns the name of the choice selected for the given number, counted starting from zero; for example, '2' will return the third selected choice." Note that the choice index can either be a number you specify in the expression, or a question placeholder, e.g. jr:choice-name(selected-at(${Photographers}, 4), '${Photographers}') or jr:choice-name(selected-at(${Photographers}, ${choice_num}), '${Photographers}') where ${choice_num} is an integer question. The jr:choice-name() function returns the label of one choice only. So if you want to get the labels for all selected Photographers into one field, you'd need a separate jr:choice-name() expression for each selection. One way to do this could be to have a separate hidden question for each choice, then concatenate all these into a final question. I will raise an issue to make the documentation clearer, as the descriptions for selected-at() and jr:choice-name() functions differ when referring to the choice index. Thanks for bring this to our attention! Hope this helps, Best, Jim

‎01-09-2022

Hi @UğurBaranSarıbaş Thanks for providing your XLSForm! The choice filter for Question 37 (need_title) is: need_title_alt=${form} ${form} is a hidden question that has no value, so no choices will be returned for this question. Could you simply remove the choice filter for Question 37, so users can see all 14 choices from the need_title choice list? I notice the same choice filter is applied to Question 48 (birim) as well. Best, Jim

‎01-06-2022

Hi @UğurBaranSarıbaş If possible, could you please share the XLSForm for your survey, so we can see how the questions and choice filters are set up? Thanks, Jim

‎01-05-2022

Hi @KatherinePadilla Thanks for your query. Both the namespaces and allow_choice_duplicates columns were included in the Standard and Advanced XLSForm templates for forward compatibility with some features we're still working on. So while these columns might have some use in the future, currently they are not important for Survey123 surveys and can be disregarded. The namespaces column would be necessary for local XLSForm conversion (where you want to use a local Python environment to convert your forms in Connect, instead of the API). We're still working out the best way to implement this. Similarly, the allow_choice_duplicates column is part of the XLSForm spec and is used to restrict duplicate choice values and we're working on how best to support this. Any queries on this, please let us know. Best, Jim

‎11-21-2021

@JoabelBarbieri That's strange! Where does your flow trip up? An image question with annotate appearance saves the final annotated image as a JPG feature attachment (including when you annotate a a map snapshot). This is similar to any other image question, so I would expect the workflow that @IsmaelChivite outlines in his blog to work regardless of how the image was saved in the survey.

Online Status	Offline
Date Last Visited	2 weeks ago

My Ideas

Latest Contributions by Jim-Moore

Re: Survey123 Use pulldata from previous question for choice filter

Re: Select one question choice info

Re: Updates to draw and annotate in ArcGIS Survey123 (September 2021)

Re: Dynamic URL in Thank You screen (not Connect)

Re: Summarize or Count Repeats inside Repeat

Re: Select one question choice info

Re: Dynamic image in Report Template

Re: How to calculate the hours between start and finish times // Como calcular las horas comprendidas entre las horas de entradas y horas de salidas

Re: Photos shown on Survey123 Field App, but not appear on Survey123 Web App after submission

Re: Choice filter is not working properly for the first record in a repeat

Re: Choice_index is not defined

Re: Choice filter is not working properly for the first record in a repeat

Re: Choice filter is not working properly for the first record in a repeat

Re: Survey123 Connect Settings namespaces field

Re: Updates to draw and annotate in ArcGIS Survey123 (September 2021)

Re: Calculating Hours between two Time questions

Re: Survey123 videos on mediaspace site presenting...

Re: Select_Multiple conditions

Re: Survey123 Report Template Error

Re: Multiple-page Survey123 form