Latest Contributions by ZhifangWang

Hi Stuart, Thanks for your confirmation.  This bug will be fixed in the next update (mid Dec.), before that, explicitly set a home location/zoom level from Settings -> Map tab in Survey123 and republish the survey can use as a workaround, please make sure there's no warning message of losing data when you republish the survey. ... View more

Hi Stuart, Thanks for the information. Would you mind checking that if your survey was published in Survey123 Connect AND there's no default location/zoom level has been set in the Settings -> Map tab? We have confirmed a bug report from Support Service yesterday that in such circumstance, the scale set in mapSettings will not work. ... View more

Hi Tiffany, Apologize for late responding, but glad to hear that the problem has been solved. Yes, in the latest 3.1 release, we provide the capabilities to report any syntax error in the report template. As a side-effect, the checking is more restrictive than before which means some templates worked before may not work now, I believe this is what you encountered. Thanks again for your feedback! ... View more

Hi all,  The bug has been fixed with a small update to the website last week, coordinates in the image viewer and feature report should work as expected now. Thanks again for all your feedbacks! ... View more

Hi Stuart, Did you mean any number between 10 and 15500 will output blank result but a number which is bigger than 15500 (scale is smaller than 1:15500) can output map image as expected? Or if the web map is in ArcGIS Online, can you please share the web map here so I can test if it works as a normal web map? Please keep in mind that currently scale cannot be used together with mapSettings, we will fix this bug in mid Dec. ... View more

Hi Stuart, Thanks for your feedback. Please see the answer here: https://community.esri.com/groups/survey123/blog/2017/07/26/introducing-custom-form-report-templates-in-survey123-for-ar… . Please be noticed "10" in your mapSettings means you zoom the web map to a 1:10 which is a very large scale, web map usually will output blank in such large scale, please check if it's a valid scale for your web map. ... View more

Hi Tiffany, Thanks for your question. The error message you observe indicates that a field in your word template cannot be matched with your survey. Prior to 3.0, this problem was being ignored by the feature report service. As of 3.1, we enforce more strict syntax validation, hence the error you see. Considering the UPDATE above, seems there are probably repeats in your survey, please make sure that the ${F_Devsize2} field can be found in the corresponding related table if it's in a repeat section (e.g. inside ${#repeat1} and ${/repeat1}) of your report template. For the Data page you see the incorrect records count, would you mind sharing the XLSForm of the survey to help us investigate the issue? Please do not hesitate to post in this thread the problems you found. Thanks again for your question. ... View more

Hi Ahjung, With the latest 3.1 release, the map generation in feature report should be more robust now, would you mind trying the original survey and template to see if it works now? ... View more

For item 4), yes, the checking process can only be performed when trying to generate report after uploading the template. In the future, we have the plan to support checking the syntax in the template without uploading a template. ... View more

Hi Julie,  I can confirm that the folder list in the Report panel should work even there's no additional folder other than the root folder for an AGO account, which means the current behavior is a bug. We will fix it in the next 3.2 release (planned in mid Jan. 2019) For your suggestion, to create a new folder in the Data page of Survey123 website without going to ArcGIS Online, I've logged it in our backlog, we will implement this when feasible. Thanks again for your feedback. ... View more

Hi Mike, 3.1 release has been available on 11/2 https://community.esri.com/groups/survey123/blog/2018/11/02/st-kilda-penguin-release-31 . Please be noticed that this bug is raised so close to the 3.1 release so we can only fix it in "the next update after 3.1 release", which is a hotfix to 3.1 release and planned no later than early Dec. ... View more

Hi Lawrence, It would be helpful if you can share some exact steps to reproduce this issue. We had few feedbacks before but currently cannot find a procedure to 100% reproduce it. Would you mind sharing more information about this issue? Does the downloading start automatically if you choose to "Save result to your account"? Does this happen to all your surveys? Which browser did you use when you can reproduce the issue? We had an issue when printing the map in report and it has been fixed. Can you please try again on the same survey/template to see if it works now? cc Claire Inbody‌ in 3.1 release, we will report any syntax error in the report template to help users fix the template more easily. As a side effect, the checking process is now more restrictly which can cause template worked previously cannot work now. Can you please check your survey to make sure the field exists in it or in the context (such as in the related layer/table if it resides in a repeat section of the template)? ... View more

Hi,  Did you see the message like "Failed to print map for ${field_2}."? There was an issue when printing map in the report and it has been fixed now. Can you please try again to see if the issue still exists? If yes, would you mind sharing the screenshot or the detailed error message? ... View more

Hi Rodrigo, Can you please try again for the same sample template (generated by the website)? There was an issue when printing map in the report and now it should be fixed. ... View more

Hi Chris, Thank you for the feedback. I can confirm it's a bug and can be fixed in the next update after 3.1 release.    ... View more