Hello.
I have created a survey in Survey123. I currently have it set as public and anyone can view it; however, if you complete the survey and try to submit it, you get the following error: "Failed to submit. - undefined". I tried making it public, not making it public but it doesn't seem to make any difference. It works great from the app. Any suggestions?
Johnathan,
I change the survey and now is working well on Firefox, on Chrome it loads for forever, IE11 loads ok but it does not autopopulate the date field.
https://survey123.arcgis.com/share/042be483aa48415188dbfb2257024a2c
Please advise,
Thanks,
Teresa Tran (Huong)
GIS Analyst - PES
Trinity River Authority of Texas
(817)493-5580 internal ext 208
tranh@trinityra.org<mailto:tranh@trinityra.org>
Webmap<https://tragis.maps.arcgis.com/>
Sharepoint<https://trinityra.sharepoint.com/sites/gis/SitePages/Home.aspx>
Hi - I will get this raised as an IE bug.
Thanks
John
John,
In Chrome it loads when the survey is public but not when is not share.
Thanks,
Huong Tran
John,
We find out we were using =NOW() in the default field and once we remove the = sign it is working in IE and Firefox but in Chrome is spinning around and doesn’t load.
Please advise.
Thanks,
Huong Tran
Hi Huong
In the survey you attached above, you were using a fixed date as the default (not now()) - this is not working in IE.
In terms of using now() you should not put an = in front of it, and if you are using a date question you should use today() instead of now(). This is because now() returns a dateTime, while today() returns a date.
Additionally, it is recommended that you put today() in the calculation field so the user can recalculate if required.
In terms of the Chrome issue - please clear your browser cache and retry. If this does not work please share your latest survey and I will test.
Thanks
John
We switched the date to datetime because we want to keep track of when they submit the survey. since they might submit the same survey multiple times in a day.
Clearing the cache on chrome did work.
In the past our setup was a feature to a tale with a relate and we were trying to force the survey to write to the table but then we were not able to submit a survey. So we switched the setup to a feature pointing to a feature with a relate, and when we publish we have the feature where the repeat are supposed to go as our first layer. Ideally the first setup make more sense but i cannot place a table before the feature when i publish. we discover in the survey123 for arcgis that when we analyze the form is pointing to the first feature in the feature service. Any advice on how to use the first setup vs the second?