I wonder if someone can help me with this?
When I add a new question to an existing survey and try to publish it I get this message
I then click on the Add the following fields when publishing button then click on Publish Survey. I then see this window below and the circle just spins and spins and nothing happens.
There is a work around but it involves recreating the entire survey again with the new questions and I don't want to keep doing that if I have to add or amend a question.
Would really appreciate any assistance with this from anyone who has managed to come up with a solution.
I am currently using version 2.8.4 of Connect for ArcGIS.
Thanks in advance
I tried your suggestion but it did not work for me. What I have done is this, I have a type called select_one SpeciesCode and have changed it to select_one SpeciesCode or other. The change is saved in the XLS form and in Connect it appears and works as expected. When I try to publish the survey that's when I get the issue I posted earlier.
Is the field being added in a repeat section? If so, there's a known issue that Connect cannot add a field if only a repeat field is being added. You can add a dummy field to the parent layer to get around this.
This used to work as you mentioned, but now it´s not possible to add a new field inside a repeat , even if a dummy field is added outside from the repeat. I have seen the problem since the last week.
Im using Survey 123 connect version 3.5.157
I'm not seeing this problem when trying to add a field to a repeat; the workaround of adding a question to the parent form still works for me. Could you provide the XLS file (ideally, the original and which fields to add)? Please feel free to e-mail me directly at jtedrick AT esri.com.
Hello @JamesTedrick ,
I tried what you suggested - adding a dummy question in the parent form to add more questions in the nested repeat tables. Interestingly, the dummy question has been added successfully, but no luck with the rest. The publish processing was hanging for hours and I had to end it. Is it an expected behavior with 3.10?
I used 3.10 version Connect.