Latest Contributions by ZhifangWang

Hi Amanda, The fix to this issue is available on https://survey123.arcgis.com now, would mind have another try? ... View more

Hi Anu, For now, you need to expose your portal to the internet to solve the issue (can open your portal's home page from any computer in the world). In the future, there's no way to create a report for surveys in ArcGIS Enterprise. ... View more

Hi Amanda, Thank you for the feedback. Unfortunately, it's a bug for the initial 3.3 release where the new feature only works for surveys in ArcGIS Online but not for surveys in ArcGIS Enterprise. Currently, we plan to have a hotfix within this week to address this issue, will let you know once the fix is available on the website. Thanks, Zhifang ... View more

Hi Lori,  No, there's no known limitation on the number of columns or number of rows of for the table. If you can reproduce the issue by just republishing the specific survey, would you mind sharing the XLSForm file (.xlsx) with us to investigate? If possible, you can just send it to my email: [email protected]  ... View more

Hi Lori, When you see the error "An error occurred while loading the page. Some features may not work.", it means an error occurred when loading the feature table in the Data page. As Evan mentioned above, it could be a browser cache issue. However, seems you have got no luck after clearing the cache. Would you mind trying to publish the same survey you mentioned in "and published a very simple survey.  Same issue: "An error occurred...."" on another computer to see if the issue still exists? If yes, it could be caused by the survey itself, if no, then it's not related to the survey itself and could still be caused by the browser's cache/AGO account settings... ... View more

Hi Anu, Actually, the error getaddrinfo ENOTFOUND is expected if you are using a portal which is not public on the internet. This is because the server of the feature report engine cannot access the item/data inside your portal. Also, please be advised when the feature report moving out of Beta, it will not support surveys in ArcGIS Enterprise anymore due to ArcGIS Online credits will be charged. ... View more

Hi all, The choice0, choice1... are the values of the behind coded value domains we initially used for Single Choice/Dropdown (select_one) questions in the survey created from the website. Since the 3.3 release, we had an enhancement to the website that when creating new a survey, we will have a better naming mechanism for the behind codes for coded value domains so that they will be valuable and easy to distinguish. For those surveys published before the 3.3 release with choice0, choice1..., I suggest the following articles to use as a workaround for including the name/descriptions of the coded value domain for the exported Excel, Shapefile. Hope these help: Problem: Exporting a feature service with domains to a CSV file shows coded values instead of descriptions  Problem: Coded value domain descriptions are not maintained after exporting data  How To: Export a feature class to a shapefile that contains domain descriptions instead of domain codes  How To: Export a table to include domain descriptions and coded values   ... View more

Hi Treg, Thanks for your feedback. I found if you create and publish a survey in the web designer, in the converted XLSForm, the today() and now() works as expected in the default column for date, time, datetime question. However, if you set them in a survey and publish the survey in Survey123 Connect (even republish the one created from the web designer), they do not work anymore. I've logged an issue in the dev repo for investigation, will get to you once if we have any update.   ... View more

Hi Kevin, Thanks for sharing the field/repeat names, I'm sure this a case we've covered in the coming hotfix. Regarding the second issue, it's out of our radar currently, would you mind sharing the XLSForm (.xlsx) and the report template file (.docx) with us to investigate? We can give you feedback once we know what's issue is.  You can send the files to [email protected] and [email protected], it would be great if you can minimize those files as long as they can reproduce the issue. Thanks, Zhifang  ... View more

Hi Lucas,  To import data from one survey to another, you may create a new survey from the same XLSForm file (and fix the field/repeat names), after publishing, use the export feature in ArcGIS Online to export your data as e.g. a File GeoDatabase, then use the append feature in ArcGIS Online to append the exported data to the new feature service behind the new survey. ... View more

Hi Kevin, Thank you for the feedback.  Would you mind sharing the field name and the repeat name to help us confirm we have this case included in the fix? ... View more

Hi Lucas, Thanks for the confirmation.  A tricky workaround is to create a new survey without the field name inside a repeat contains the repeat name and then import the data into the new survey. It's inconvenient unless you have to generate reports anyway. We have planned a hotfix to address this issue, it will be available in the week after the Dev Summit. Please let us know if you have any other concern. Thanks. ... View more

Hi Lucas, Would you mind sharing the exact error message raised by the custom report feature? We had a known issue that the report template cannot work if the field name inside a repeat contains the repeat name (parent layer name), not sure if it's the issue you've encountered. ... View more

Hi Piero,  We've made an enhancement in 3.3 release to allow editing the thank you screen content of Survey123 Connect surveys directly in the Design page of Survey123 website, just as you edit it for the surveys published from the website. Please be noticed after editing and publishing the survey on the website, you have to use 3.3 or higher version of the web app to see the result.  If your survey is version locked, you either need to turn off the version lock in the Settings page of the website or republish the survey in Survey123 Connect 3.3 or later. If your survey is not version locked (always use the latest web app), you should see the modification of the thank you screen content automatically. The 3.3 release is planned before the Dev Summit, please stay tuned with our release blog and doc to find more details. Thanks again for your feedback! ... View more

Hi Oussama,  We've made an enhancement in 3.3 release to allow editing the thank you screen content of Survey123 Connect surveys directly in the Design page of Survey123 website, just as you edit it for the surveys published from the website. Please be noticed after editing and publishing the survey on the website, you have to use 3.3 or higher version of the web app to see the result.  If your survey is version locked, you either need to turn off the version lock in the Settings page of the website or republish the survey in Survey123 Connect 3.3 or later. If your survey is not version locked (always use the latest web app), you should see the modification of the thank you screen content automatically. The 3.3 release is planned before the Dev Summit, please stay tuned with our release blog and doc to find more details. Thanks again for your feedback! ... View more