I recently had a need to modify a survey schema (Field Length from 1000 to 20000 DON'T ASK! HAHA!!) that had been originally developed using Survey123 Web Designer. Of course, all the GeoNet posts state, this could not be accomplished once the survey had been published.
I developed a 'Test' Survey utilizing the exact same attributes and schema from the original survey and submitted numerous surveys through the browser, field app, and desktop app. All the submission data was then exported into a .csv file to back up what had been submitted.
In the survey123.com website 'Design' tab, I duplicated each question that needed to have it's schema modified. The Web Designer automatically labeled the copies with the original name plus '- Copy'. Each duplicated question's label was then edited to remove '- Copy'. Thereby making a carbon copy of the original question including schema (For now).
Then the old questions were deleted by previously identifying their number within the entire survey ensuring the new questions were not accidentally deleted. A popup (Shown Below) wanted a confirmation of the deletion and then stated any previously captured data could be deleted or not during the publishing phase. I clicked 'Yes' and did not check the 'Don't ask me to confirm again' box, because I always like a safety measure in place to stop potential accidental changes.
Once the new questions were in place, the old ones deleted, and the survey saved, I clicked the 'Publish' link and then clicked the 'Modify schema' link. The schema for the survey now allowed me to modify the 'Field Length' for the new questions. I then clicked on the 'Publish' link.
A popup appeared asking me if I wanted to keep or delete the previous answers for the old questions. If I wanted to delete all previous answers for each question than I could have marked each individual question, but I just kept the fields unmarked and clicked the 'Publish' link.
I opened this modified survey through the browser, field app, and desktop app and completed numerous submissions within each of them. I ensured this new survey could handle the larger field length by pasting text that was greater than the previous 1,000 field length, text 1 character length less than the maximum, and text greater than the new schema.
Within the desktop app, any entries greater than the defined 'field length' could not be published, whereas the browser allowed entries greater than the defined schema to be copied/pasted and submitted. This was an interesting find that the browser did not adhere to the survey's schema.
Under the 'Collaborate' tab within the Survey123 website, all previously submitted surveys had harmoniously merged with the new submissions as though the changes never happened. I verified this by exporting the new data set and comparing it against the first .csv.
- Even though a new hyperlink was developed by the republishing of the survey, I found that the old hyperlink still worked and utilized the new schema. Since I had just published the survey last week, this proved invaluable since personnel were already utilizing it within the various apps.
- The data was exported before modifying the schema to ensure none of the previous submissions were lost for the actual "Live" survey when I applied this modification.