Latest Contributions by ZhifangWang

Hi Jay H‌, The fix mentioned by James is available on our beta website https://survey123beta.arcgis.com , would you mind trying it out to see if it works for you? Regarding the original showing HTML code issue, would you mind sharing a test survey or the XLSForm which can reproduce the issue with us? Thanks, Zhifang ... View more

Hi Alex, BUG-000125151 has bee fixed in the 3.9 release.  Thanks again for your feedback. ... View more

Hi All, This issue has been fixed in the 3.9 release. Thanks for all your feedback! ... View more

Hi Hannah, Thanks for your feedback. We have identified a similar issue that changing the thank you screen content and publishing the survey does not take effect for some Connect surveys, this has been fixed on our beta website now. Would you mind trying to change/publish your survey there https://survey123beta.arcgis.com to see if it works for you? Thanks, Zhifang ... View more

Hi Maxime Demers‌, Currently, the web app JavaScript API is not available offline. And it is based on iframe for now. One of the goals of the web app JavaScript API is to make the communication with the iframe (for now) transparent to developers, so you can still utilize the same code even we don't use an iframe in the future. Would you mind sharing what is your use case or what you want to achieve through the API? Thanks, Zhifang ... View more

Hi, Thank you for the feedback. Please be advised that there will be a change in the coming 3.9 release where objectId URL parameter is going to be replaced by globalId, see https://community.esri.com/groups/survey123/blog/2020/02/19/upcoming-changes-to-survey123-web-forms-query-parameters  for details. ... View more

Hi Rob, Thank you for the feedback. The issue is currently "in consideration" in our backlog, I've added your comment to our internal issue. In the meantime, it would help to prioritize the issue if you can reach to Esri Support about this bug: BUG-000117569 Thanks, Zhifang ... View more

Hi All, This issue has been fixed in 3.8 hotfix1 which is available on the Survey123 website now. For surveys published from now on in the web designer, the geopoint question can work in Survey123 field app as previously. For surveys published after 1/21 (3.8 release) and before today (2/11, 3.8 hotfix1), they need to be republished again in the web designer if you want to use the map of geopoint question in the field app. Thanks again for all your feedback! Thanks, Zhifang ... View more

Hi Mervyn, We fix to this issue is now available on the Survey123 website, you should be able to generate the report without doing any additional steps. Thanks, Zhifang ... View more

Hi Jeff, Thank you for the feedback. As far as we know, it's only the > (greater than) or < (less than) sign in question label, choice label, or the submit button text will cause this issue. You can track this bug in BUG-000128390. We will have a hotfix for this issue in a few days, after the fix, your survey should automatically recover to one of the following status: If the survey is created after 3.8 release on 1/22, recovers to the last published status if it is published already recovers to an empty survey if it's never published. (unfortunately, this is what we can do the best) If the survey is created before 3.8 release, recovers to the last draft or published status before 1/22. Thanks, Zhifang ... View more

Hi Mervyn Lotter , Would you mind sharing when is the first time you saw this issue? before this issue, did you make any change to your survey or the template recently? We have identified a bug after the recent 3.8 release on 1/22, which will raise the exactly same error message as you mentioned. Below are the conditions to reproduce the bug: The survey is created from an existing feature service (seems this is qualified for your survey) The underlying feature layer has not enabled owner based access control (OBAC) or it does not have the edit date field (which records the last edit time of the feature). Before previewing or generating the report, you didn't manually sort any field in the feature table of the Data tab. Can you please check if this is what you encountered? Note: if you can work around this error by just manually sort any field in the feature table (no matter ASC or DESC) before previewing or generating the report, then you should hit this bug. Thanks, Zhifang ... View more

Hi Jeff Carney‌ / Kanin Sangcharoenvanakul‌, Thank you for your feedback and the investigation. Jeff,  Can you please confirm your broken survey created in the Survey123 website contains any special characters (e.g. > greater-than sign or < less-than sign) in any question label or choice label? We have identified a bug in the 3.8 release with the following reproduce steps: 1. Create a new survey in the Survey123 website or open an existing survey that created in the Survey123 website. 2. In the Design tab, do any change and save the survey or directly save it without any change. 3. As long as there are any "<" or ">" characters in a question label, choice label, submit button text, the survey will be broken and you cannot open it anymore in the Survey123 website. In the Design tab: it keeps loading, in other tabs, you may see the error message "The survey does not exist or is not accessible." Please let me know if this is what happened to your survey. Thanks, Zhifang ... View more

Hi Javier, Can you please confirm that it's only the field name ${Grants} in your report template and your didn't reference it by layer name while error message returned by the report engine includes the layer name before the field name as ${2020_Prescribed_Fire_Grant_Application_MASTER.Grants} ? If this is true, would you mind sharing some detailed steps to reproduce the issue? I've tried the following steps but there is no error during the syntax checking or generation of the report. 1. Create a new survey in Survey123 Connect which name starts with a number. For example, "2020_startWithNumber". 2. Leave the only text question "example" in the XLSForm untouched and publish the survey.   * I can observe that the underlying feature layer name is "_2020_startWithNumber". 3. Submit a record in either the web app or the field app. 4. Try to generate a feature report by using the default sample report template, which contains the placeholder "${example}". Reproduce steps would help us a lot to investigate the issue. Thanks, Zhifang ... View more

Hi James, Thank you for posting the feedback. This is a bug we just fix in the next 3.8 release, you can now try the fix on our Beta website (need to apply the Survey123 Beta program in Early Adopter Community). Would you please have a try and let us know the result? Thanks, Zhifang ... View more