Latest Contributions by ZhifangWang

Hi @Sghimire , @abureaux , Could you share any job IDs for jobs that timed out or failed with 50x errors recently? ... View more

Hi @hello_hello , The syntax in your report template looks good. Survey123 uses the attachment keyword to determine which question each attachment is associated with. Just to confirm, the keyword you added to the attachments is "QS_VIDEO_image" — without a period at the end, correct? Also, would you mind checking in edit mode on the Survey123 web app to ensure the keyword is set correctly? You can use the URL: https://survey123.arcgis.com/share/<surveyId>?mode=edit&globalId=<recordGlobalID> to verify if the attachments are loading properly. If they aren't, you can use your browser's developer tools to investigate further. Once the attachments load correctly in the Survey123 web app, they should also appear in the report. ... View more

Hi @abureaux @lklun , Thanks for sharing the detailed information. We deployed a hotfix for this issue around 8:30 PM PDT on July 7. As a result, some jobs may take longer than usual to complete. Are you still experiencing this issue? To help us investigate further, could you provide some more specific information? Do the affected reports share anything in common? For example, do they all contain: a web map with many layers or features, or a specific report template? How long does this situation last? If possible, could you try running one of the problematic reports on the Survey123 Beta website (https://survey123beta.arcgis.com)? If it fails or runs slowly there, please share the job ID. That would help us look into the details. Thanks, Zhifang ... View more

Hi @JuanTomásMartinez17 , It is not possible to pass URL parameters to the survey in the Survey widget currently. Would you mind sharing more details of your workflow to help us understand the potential enhancement to the Survey widget? For example, what settings you need in the Survey widget in additional to passing URL parameters? ... View more

Hi @JustinConnerWR @MCostley , The fix to BUG-000177676 has been deployed to the Survey123 website earlier today. Please let us know if you still observe any issues when printing a report with a map.   Thanks, Zhifang ... View more

Hi @JustinConnerWR , We confirmed that a bug was introduced with the Survey123 July 2025 Update: printing a report that contains a map will time out if the map includes the same feature layer specified in the featureLayerUrl parameter to the report API. For example:. For example: If you are the survey owner and has a web map references the survey's source feature layer, the issue occurs when you print a report on the Data tab of the Survey123 website. This is because the Data tab uses the survey's source feature layer if you logged in as the survey owner. If you are a stakeholder of the survey and the web map in the report references the _result view of the survey, the issue occurs when you print a report on the Data tab. This is because the Data tab uses the _result view layer of the survey if you logged in as a survey stakeholder. This was reported as BUG-000177676 and will be fixed in a hotfix early next week. Could you confirm if this matches your workflow, or are you seeing a different scenario? ... View more

Hi @LeeBrannon1 , In the Survey123 July 2025 Update, the related change we made for the Address question type was using the latest ArcGIS Maps SDK for JavaScript, it should not change behavior of the question type. Would it be possible to share a public survey URL that reproduces the issue so we can investigate further? You can send me a direct message with the survey link. ... View more

Hi @ANRGIS , Did the "out of memory" issue occur before this fix? If it occurs consistently, can you please share the XLSForm file with me via a direct message? ... View more

@MariannaTheodorou , As Steve suggested, ChatGPT or a similar assistant could help with this. Based on your expression, the following should work: concat('<p>', (int(substr(${a_03_time_spent}, 0, 2))*60)+int(substr(${a_03_time_spent}, 3,5)), '</p>') Note: the fix for this issue has been deployed to the Survey123 website earlier today, so your survey should work automatically without needing to apply this workaround. ... View more

Hello everyone, The fix for this issue was deployed to the Survey123 website earlier today. Original surveys affected by the issue should now work automatically. Thank you again for your feedback. ... View more

Hi @ChessClaire , This issue exists in the survey itself so you can test by directly opening it in the Survey123 web app https://survey123.arcgis.com/share/<surveyItemId>. On the other hand, you can load the survey using the Survey123 beta web app in the widget of Experience Builder app by setting URL parameter https://experience.arcgis.com/experience/<itemId>?survey123=env:beta , which will use Survey123 beta envrionments for the Survey widget. Please let us know if you still observe any issue in your workflow. ... View more

Hi @JeremyMulcahy-Hill , Do you mean the Survey123 feature report? If yes, you can use the syntax drawingInfo to customize the symbol on a map. Links may help: Help topic in the documentation Survey123 Tricks of the Trade: Print web maps in reports ... View more

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