Latest Contributions by AlexaTodd

‎01-31-2024

We've been having this issue since March of 2023. Several crews update case data daily on iPads in the field using Field Maps. The form is configured to require certain fields. Due to the lifecycle of the record, these fields must allow nulls. At random, about 5% of the records updated by crews record a required field as null, even after they have successfully submitted the edits. Our evidence is in the edit tracking—records with the crew account as the last editor, yet the required fields are still null. Crews do not have access to the data any other place than in Field Maps using the forms. We have an escalated bug open with Esri: BUG-000160038. (Important to note, after doing more work investigating the bug, we learned information that isn’t in alignment with the original description/source of the bug—primarily that the issue does not result from simultaneous use of the underlying data.)

‎08-21-2023

Thank you for your response! It worked to remove the extra quotes. And simpler too. 🙂

‎08-16-2023

I'm having trouble pulling data from a feature layer in AGO into my survey123 connect using a barcode to get the where clause value. When I hard code the id into the where clause rather than referencing it by the barcode variable, it pulls the JSON from AGO. I've added checks into the survey and the where clause that is built using concat() to combine the query with the value from the barcode appears the same as when I hard code the value. Attached is an example from my xlsform. I tested the survey on my iPhone and scanned a barcode on the computer screen that I created using a free online generator: Any ideas why the barcode is not working for pulling the feature layer JSON? Thanks!

‎04-16-2019

I think I found a bug that has been introduced in newer versions of Survey123. Has anyone else observed the following? When testing my survey in version 3.3.64, the requirement that at least one select_multiple is selected does not work when a new repeat is added. Only when the question is visible (the currently displayed repeat) does submitting the survey produce a requirement error. Attached is the XSLForm. This survey works fine from Survey123: version 2.8.2.

‎04-15-2019

That works! Thank you. Creating a new group around the questions and moving the relevant formula to the "begin group" row made the requirement function correctly on the question within the group.

‎04-15-2019

Still having issues with the solution. This section is inside a repeat. As far as my testing indicates, the calculated question with a constraint works only if it is not hidden. Is this true? Must a question be visible to trigger a validation error? EDIT: When the question entry that is not valid (i.e., no subcategories are selected) is visible in the displayed repeat, the validation works. However, if the question entry that is being displayed is valid, then the validation is not triggered for the other (not visible) repeat entry.

‎04-12-2019

Found a solution to this problem. Attached is the simplified form. Summary: Rather than using a filter for each category, I added a new choice list for each and added them as separate questions that appear when relevant. At this point, the requirement was not working to ensure at least one from the multiple choice list was selected. The solution was adding an additional hidden field that calculates the count of the selection using an if statement to determine which list is relevant, and if no list is relevant outputs 1. This was important for allowing categories without subcategories to be valid on their own. All of these questions are null field types, so that they are not recorded in the database. The subcategories are recorded in the database in a hidden question that uses a calculation to join any subcategory selections. Details: Create a new choice list for each target pest w/ subcategories Add a question for each pest w/ subcategories with the following parameters: type select_multiple required yes relevant selected(${TargetPestCategories}, '[pest w/ subcategories]') bind::esri:fieldType null Add a hidden question with the following parameters: constraint .>=1 required yes calculation if(selected(${TargetPestCategories}, 'Habitat_Restoration'), count-selected(${SelectedHabitatRestoration}), if(selected(${TargetPestCategories}, 'Indoor_Pest'), count-selected(${SelectedIndoorPest}), if(selected(${TargetPestCategories}, 'Plant_Disease'), count-selected(${SelectedPlantDisease}),1))) bind::esri:fieldType null Set up the TargetPestSubCategory field with the following parameters: type hidden required yes relevant selected(${TargetPestCategories}, 'Habitat_Restoration') or selected(${TargetPestCategories}, 'Indoor_Pest') or selected(${TargetPestCategories}, 'Plant_Disease') calculation join(',',${SelectedHabitatRestoration}, ${SelectedIndoorPest}, ${SelectedPlantDisease})

‎04-08-2019

I've created a copy of my survey with the portion I'm having issues with. Please see the attached table where I have attempted to solve the problem with the addition of a repeat. Now the issue is adding logic that links the two questions so that if the category changes, the subcategory is reset. Is it possible to combine jr:choice-name with regex to get the name from the label and use this to define what is relevant?

‎04-08-2019

Thought I found a work around, but now I'm dealing with another issue. To get multiple selections of the subcategory, I've added a repeat that is also conditionally relevant depending on the category that is selected in the first question. The problem is if the user changes the first question after submitting a repeat, the choice(s) that is/are already selected remain, and the final result is a mix of choices that do not all match the first category. Is there a way to ensure the selected repeats all match the appropriate filter for the final relevant category? Perhaps using jr:choice-name?

‎03-29-2019

I need to change the type of the conditional question ("Target pest subcategory") so that more than one can be selected: However, the filtering does not work when I change the type from select_one to select_multiple: QA (TargetPestCategories) references 7 options from the 'choices' sheet (image below). 3 of these options have subcategories that are within another list referenced by QB (TargetPestSubCategory). QB contains a relevant query... selected(${TargetPestCategories},'Plant_Disease') or selected(${TargetPestCategories}, 'Indoor_Pest') or selected(${TargetPestCategories}, 'Habitat_Restoration') ...and a filter: filter=${TargetPestCategories} This is what the survey looks like when I remove the filter: Any ideas how I can filter the conditional question while still allowing for multiple selections?

Online Status	Offline
Date Last Visited	a month ago

My Ideas

Latest Contributions by AlexaTodd

Re: Required Fields Allowing Nulls to be Submitted

Re: No result from pulldata @layer with where clause with scanned barcode value

No result from pulldata @layer with where clause with scanned barcode value

Bug Found in Survey123 Version 3.3.64 That Concerns Repeats.

Re: Using XLSForm for Survey123 Connect, how do I create a choice filter on a cascading multi-select?

Re: Using XLSForm for Survey123 Connect, how do I create a choice filter on a cascading multi-select?

Re: Using XLSForm for Survey123 Connect, how do I create a choice filter on a cascading multi-select?

Re: Using XLSForm for Survey123 Connect, how do I create a choice filter on a cascading multi-select?

Re: Using XLSForm for Survey123 Connect, how do I create a choice filter on a cascading multi-select?

Using XLSForm for Survey123 Connect, how do I create a choice filter on a cascading multi-select?

Re: Required Fields Allowing Nulls to be Submitted