Latest Contributions by ZhifangWang

Hello everyone, We have identified an issue in the Survey123 May 2025 Update: when using Survey123 Connect, a calculation for a readonly text or note question may not function as expected and can even cause the survey to fail to load. Current workaround: For any note or readonly text question using a calculation, wrap the calculation in HTML <p> tags. For example, if the original calculation is ${int1}, change it to concat('<p>', ${int1}, '</p>'), then republish the survey. Alternatively, for non-production surveys, use the beta version of the Survey123 website at https://survey123beta.arcgis.com, which includes a potential fix. Note: ?version=latest in URL is the only supported value in the documentation. Unless you have fully tested, using an old version number may cause other issues. We appreciate your understanding and have planned a fix for early next week to address this issue. Please let us know if you still observe any issues on the beta website. ... View more

Hi @RachelS , If your report is using PDF or Microsoft Word format, you can achieve this by printing a feature report. Assuming your feature layer name is layer1 and the object ID field is objectid, the syntax ${layer1 | stats:"count,objectid"} will output the record count in the input to the report from the layer. (${layer1 | where:"1=1 !important" | stats:"count,objectid"} will always output count of all records in the layer) Some links may help: Understanding Survey123 Feature Reports Survey123 Tricks of the Trade (Live): Automate Reports For example, send yourself a report via email every three months. Report template documentation ... View more

@PierreloupDucroix , Does the same error occur consistently? If you see it again, could you submit feedback using the thumbs up/down icon so we can investigate? ... View more

@LouisaM , Can you please confirm that your Survey123 organization settings are as below? If yes, can you share a screenshot of the Design tab on the website? ... View more

Hi @hjargis , We identified an issue that if there are any broken images referenced in the survey, the web designer would prevent the survey from publishing and report the `{}` error. A fix to this issue has been applied to the Survey123 website, can you please try again to see if it works for you? Note: a broken image now will not prevent publishing and can display in the survey design so you can remove or fix it manaully. ... View more

Hi @philip_worrall2 , We identified an issue that if there are any broken images referenced in the survey, the web designer would prevent the survey from publishing and report the `{}` error. A fix to this issue has been applied to the Survey123 website, can you please try again to see if it works for you? Note: a broken image now will not prevent publishing and can display in the survey design so you can remove or fix it manaully. ... View more

@hjargis , There have been similar cases reported to our support service team, and we are still working to determine the details. Could you reach out to Esri Support Service to assist with the investigation? ... View more

Hi @RABConsultants , There is a new method mapFilters in report template to filter out features in a layer in web map. Please see  https://community.esri.com/t5/arcgis-survey123-blog/survey123-tricks-of-the-trade-print-web-maps-in/ba-p/1537166 and let me know if this could help with your workflow. ... View more

@ISP_graynic , In addition to contacting the Esri Support team, if you can reproduce the issue with a minimal XLSForm file, please share it with us for a quick investigation. ... View more

@RichardHumphries , It would be better to specify a web map item ID explicitly in the report template, see https://community.esri.com/t5/arcgis-survey123-blog/survey123-tricks-of-the-trade-print-web-maps-in/ba-p/1537166.  If not, the map could change based on the question design in the survey or the default map used in the org. ... View more

Hi @AnthonyJonesRSK , Thank you for your patience. From the information you shared, we identified to issues after the Survey123 February 2025 update since last week: A file question inside a repeat cannot load completely in the 3.21 web app. For the edit mode (?mode=edit) in the 3.22 web app, if setting the default value for a note question type using the `?field=` URL parameter, the web app becomes unresponsive. This has been reported as BUG-000174625. We have applied fixes to both issues on the Survey123 beta website, could you verify to see if the fixes work for you? To test the fix to the second issue, append the URL parameter `?survey123=env:beta` to the URL for your Experience Builder app. This URL parameter is used for development work and will load the Survey123 web app from the beta website. It will use the 3.22 web app on the beta website as your survey has been already published in the 3.22 Survey123 Connect To test the fix to the first issue, in addition to appending the URL parameter `?survey123=env:beta` to the Experience Builder app, you need to open the browser's developer tools and locate the Survey widget's iframe in the HTML, and then update its src (the URL of the embedded Survey123 web app) to append the URL parameter `version=3.21`. This will load the Survey widget using the 3.21 web app on the Survey123 beta website. Please find attached the details for the above tests. If you have a local copy of the installation file of the 3.21 Survey123 Connect, you can install it and republish the survey to revert it to the 3.21 version. ... View more

Hi @cfransen , Thank you for sharing the XLSForm and report template files. We have identified the issue: it is caused by the "esriFieldTypeString" setting in the bind::esri:fieldType column for a "start" question type. The question in your survey uses the "time" setting in the bind::type column, which is essentially the same to a "start" question type. We are currently working on a potential fix for this issue and will keep you updated on the progress. Unfortunately, there is no easy workaround for this issue unless you remove the "esriFieldTypeString" setting in the bind::esri:fieldType column and republish the survey. However, please proceed with caution, as this action will change the underlying feature layer schema and may result in data loss. ... View more

Hi @AnthonyJonesRSK , The Survey123 website was updated yesterday, which may have caused this issue. I was able to reproduce the problem in an Experience Builder app as you described. We are currently working on a potential fix and will keep you updated on the progress. In the meantime, to work around this issue, please temporarily set the version lock for this survey to false. This will allow you to remain on version 3.21 until the fix is implemented. ... View more

@cfransen , The Survey123 website just got an update yesterday, which may have caused this error. Could you please share with us a minimum survey (or XLSForm file) and the report template that can reproduce this error? ... View more