AnsweredAssumed Answered

Survey123: why does updating domains fails?

Question asked by htouyeras_1 on Jul 5, 2018
Latest reply on Mar 22, 2019 by senyedygoldneresri-ca-esridist

Our fieldcrew is extatic with Survey123, its ease of use in the field and back in the office. Their needs are growing day by day, and I am regularly requested to update existing survey designs.


The designs so far are made with Suvrey123Connect (v.3.0.58). Most fields are "Select_one" or "Select_multiple" fields, with the domain documented in the "Choices" tab of the XLS file.


I recently modified two domains:

   -Domain A: added 103 lines (pair of code and alias value)

   -Domain B: corrected an erroneous code value, that duplicated another one.


I successfully saved the spreadsheet and re-published the form. No warnings, no problem - odd, as chainging domains is supposedly a structure change that should/would/might require the webservice to be deleted and recreated from scratch.


When filling the form with S123 field app, the new values are present in form.
    -I can select from the new values in the two fields using each domain, and post my field survey.


When I export the data to a file geodatabase, both domains are incomplete: Domain A is lacking the 103 new values, and Domain B does not contain the corrected coded value (the pair code/alias is missing, supposedly because the erroneous entry meant 2 identical codes were submitted to the database, and only the first one was accepted). i.e. the correction made in the XLS form did not carry over in the webservice underlying datastructure


Can I update and the domain contents of my survey without publishing the survey design to a new survey (this breaks all maps, apps, and dashboards built upon the existing webservice)?

...If yes, how?

...If no, why did I receive no warning when publishing the survey design, and why was my webservice not deleted/recreated by the publishing process?


To be complete, the publication to a new URL is successful, with correct domain contents applied in the form and in the resulting geodatabase.


Many thanks for you help and advice!


With kind regards,