Latest Contributions by ZacharySutherby

Hello Lisa Dygert‌,  I know you had said you tested cascading selects and it was not working but I believe it may work out. If you would like there is a sample in Survey123 Connect if you were to create a new survey and select "Samples" on the left hand side, there is a sample survey called "Cascading Selects" that displays the workflow and functionality. (I have also attached a copy of the XLSFrom to this post too) An alternative workflow may be to use the pulldata() function to pull district values from a csv file.  Please use these links for reference:  https://community.esri.com/groups/survey123/blog/2016/10/27/the-pulldata-function-access-external-data  Formulas—Survey123 for ArcGIS | Documentation  As for the 1:M relationship between counties and districts is the schema for the service already created? Meaning are you creating a survey based on an existing feature service that has this relationship set up or are you creating the schema from the XLSForm and creating a hosted feature service when publishing the survey?  Thank you,  Zach  ... View more

Hey Leonard,  I am glad removing the ObjectID from the XLSForm is working out!  For the error report, I was originally testing in 3.10.198 but just updated to 3.10.222 and the workflow was the same in both. When the error is thrown in the publishing log if you click on the block with the error it will pop up the report window:  Thank you,  Zach  ... View more

Hello,  Thank you for passing along the XLSForm! In taking a look at the XLSForm it looks like there are a few duplicate field names down in the groups. On lines 52-56 within the dpr_value group, the question names are the same as the questions on lines 42-46. This is the reason the publishing is failing when adding to the service definition because it can't add fields with the same name to the service.  I had changed the questions in lines 52-56 to value3_XXXXX and the form published as expected to my ArcGIS Online Organization.  Alternatively, if you would like to keep the same field names you can switch either the value2 or drp_value groups to a repeat so that those fields are added to a related table instead of the root feature service.  Thank you,  Zach  ... View more

Hello Sanjeevi,  In taking a look at the XLSForm it seems that the labels were not formatted text even though they looked like they were.  When I would double click on the label it would pop to the right-hand side of the cell indicating they were numeric. In a separate column I had used the function =TEXT(<cell>,"0") to convert the numbers into integers. Documentation link.  I then copied the text cells and pasted them back into the column they were supposed to be and they worked as expected.  For your second question, the documentation says "External selects are designed to work with choice lists associated with a cascading select only. Only choices with an applied choice filter will be added to the itemsets.csv file."    This means that external selects are designed to work in conjunction with cascading selects. The external_choices tab is not invoked until there is at least one select_one question with a choice_filter.  Please use James's comment here for reference: https://community.esri.com/thread/214070-external-select-lists#comment-768979  What I had done to modify your survey was to move the villagename choice list to the choices tab but kept the plot number choices on the external_choices list.  I then saw an issue where the plotnumber question was grey and did not have any choices. This was because in the same documentation linked above in the cascading selects section it says that values used in the name field of the choices sheet must be text and not numeric.  I had changed the name of the villagename choices to a,b,c,d,e for example and once I did that the form worked as expected. Please find attached a copy of the XLSForm.  Thank you,  Zach  ... View more