Latest Contributions by ZhifangWang

Hi Colin, Thanks for the tests and the above information. Unfortunately, there is nothing you can do to make the format works as you expect until we deliver the fix to this bug. You can track the status at BUG-000117569 Survey123 for ArcGIS surveys with internationally formatted date questions display submitted responses in the US date format in the attribute table. After fixing, the sequence for deciding the format would be: language setting in the XLSForm (if any) > language/format settings in the user profile in ArcGIS Online > browser setting (for a public survey). Thanks, Zhifang ... View more

Hi James, There is no known issue about the usage of appearance:"multiline" for a multiline text question. Would you mind sharing your XLSForm and the report template (a simplified version that can reproduce the issue would be better) for us to investigate? Thanks, Zhifang ... View more

Hi Liz, It will be great if you can send me a zip package that contains all files in the survey folder downloaded via Survey123 Connect, which includes the raw "form.json" authored from the Survey123 website. Thanks, Zhifang ... View more

Hi Maximilian, Can you please try to identify if there is any issue in the browser after clicking the Submit button (which triggers the applyEdits request to the feature service) by using the browser's developer tools? You can get the most useful information there. For example in the following screenshot, there is a POST request failed and marked as red color since the webhook set in Integromat no longer exists. Thanks, Zhifang ... View more

Hi Joe, Thanks for reaching to us. If you mean the popup in a web map, you can configure the popup in Map Viewer by using the pattern {fieldname} to insert a field value dynamically in the popup. I found a clue in the doc Integrate with other apps—Survey123 for ArcGIS | Documentation and tried the settings in the attached image below. Would you mind having a try to see if this is what you want? Thanks, Zhifang ... View more

Hi Alli, Thank you for reaching to us and attaching your survey info. By looking into your XLSForm and the report template, it seems the field name store_cs10locationgps  is not correct and cannot be found in your XLSForm. Would you mind using the correct field name cs10locationgps and try again? Please see the attached image for details. Thanks, Zhifang ... View more

Hi Colin, Thanks for your feedback.   The fix to this bug will respect the date and number format setting in the user's profile, and in the Survey123 website/web app, the setting in user's profile takes precedence over the org's setting. Does this make sense to you?     Thanks, Zhifang  ... View more

Hi Liz,  Seems your issue is similar to the BUG-000125687. Can you please upload a screenshot of the modify schema dialog (Publish->Modify schema) which scrolls to the question "Funder"? This helps us to confirm if it's the same issue with the above bug. Although we fixed the bug and will auto-truncate names for any choice which is longer than 32 characters, there is a chance that a longer than 32 character name is input manually in the modify schema dialog. In this way, we won't change it until you manually fix it. Thanks, Zhifang ... View more

Hi Kevin, The Survey123 website just got an update which is available on our beta version of the website: https://community.esri.com/groups/survey123/blog/2019/10/30/survey123-early-adopter-program-updates , you can find a new Preview capability for the feature report, which can be utilized to refine your report template without charging credits. Also, generating a report in PDF format is available there too. Please feel free to post your (technical) feedback about these new features in the website forum in EAC. Thanks, Zhifang ... View more

Hi Kerissa Reedy‌, Just FYI, the latest Survey123 Beta update is just published on EAC, in includes a dedicated post for demonstrating the new PDF/preview capability of the feature report which is available now on Survey123 beta website: https://survey123beta.arcgis.com. Please have a try and let us know what do you think by posting on the new beta website forum. Thanks, Zhifang ... View more

Hi Heather, Since the error only happens during generating the report but not checking the syntax, seems that it could be a relatively complex situation and also may relate to the data structure. In this way, I would suggest that it's better to open an Esri Support ticket for further investigation, also confirming the bug through Esri Support would raise the priority for the issue. Thanks, Zhifang. ... View more

Hi David Cook‌, The web app accepts the paramter ?token= , so you can append a valid token to skip the sign in screen. In this way, you need to take care of the token so it will not be utilized by malicious users. ... View more

Hi Kerissa Reedy‌, PDF format support in the Feature Report is planned in a very near future release and will be available soon in the Beta Community first. Please stay tuned with our announcement in the Beta Community and also the product release blogs. Any feedback in the Beta Community would be appreciated. Thanks, Zhifang ... View more

Hi Javier, Thank you for the detailed information and also sharing the workaround which may help others. I can reproduce the issue by creating a simple survey whose name starts with a number and also contains a repeat from Survey123 Connect, then try to reference a field in the parent layer by using the survey name inside the repeat section in the report template. So for your question, yes, I can confirm that the issue is caused by the additional underscore in the behind layer name which is not the same as the survey name. In addition to your workaround above, could you try to simply add an underscore in the main layer name in your original template to see if it works for you? For example, instead of using ${2020_Prescribed_Fire_Grant_Application_MASTER.Grants}, use ${_2020_Prescribed_Fire_Grant_Application_MASTER.Grants} to access the field in the parent layer inside a repeat section. The report engine is designed for being able to work with a feature service directly (even without a survey), so using the correct layer name should work.  Please let me know if it does not work for you. Thanks, Zhifang ... View more