Latest Contributions by ZhifangWang

Hi dan becker‌, Thanks for the suggestion. We are working on a workaround in Survey123 to bypass the issue in ArcGIS Enterprise 10.8. In details, if supportsPagination is false or Enterprise version <10.8.1, we will eliminate the resultOffset and resultRecordCount in the request of the report engine. This workaround should be available soon on our Beta website first, if it works well, it will be planned for the Production website later this week. Thanks, Zhifang ... View more

Hi EnelGreenPowerNA, The fix for feature report issue is on Survey123 website https://survey123.arcgis.com now. Thanks again for your feedback. ... View more

Hi Anthony Jones‌,  The fix for your feature report issue is on Survey123 website https://survey123.arcgis.com now. Thanks again for your feedback. ... View more

Thanks for the additional information, we just figured out that the bug applies to feature service that does not support /queryAttachment (ArcGIS Enterprise < 10.8) ... View more

Hi dan becker‌, Thanks for your feedback and the detailed information. Since you mentioned that it's ArcGIS Enterprise 10.8 you are using, I can confirm and share the details that this issue is caused by the combination of the following two: In the latest update of the Survey123 website, we use /queryAttachments instead of attachment info as long as the feature service's supportsQueryAttachments is true (Enterprise >=10.8). Also, we will use pagination approach to query all attachments in case the total account exceeds the maxRecordCount, as long as the feature service's supportsPagination is true. Your ArcGIS Enterprise satisfies both. In ArcGIS Enterprise 10.8, there is a bug that if resultOffset and resultRecordCount are used in queryAttachments, ‘Pagination is not allowed unless ''supportsPagination'' is true.’ error occurs even supportsPagination is true in the layer. You can tell this by trying in the service directory as below. This issue is fixed in the coming ArcGIS Enterprise 10.8.1    From Survey123 perspective, we are trying to figure out a workaround for the issue in ArcGIS Enterprise 10.8 so it will not affect feature report users. Thanks, Zhifang ... View more

Hi Aurelija Ruta Viluckyte‌, We have identified the issue and are working on the fix, will let you know once the fix is available to test. Sorry for the inconvenience.  ... View more

Hi Deena Bowman‌, Thanks for the feedback. We've noticed this issue and looking into a hotfix to include the fix. Before that, you can turn on the version lock in Settings->Version of the Survey123 website to set the survey use the previous web app other than 3.10 as a workaround. ... View more

Hi Richard Hammond‌, Would you mind sharing the XLSForm with us so we can look into the cause of the issue? ... View more

Hi Aurelija Ruta Viluckyte‌, Can you please share which version of ArcGIS Enterprise you are using? ... View more

Hi EnelGreenPowerNA, We updated the beta website https://survey123beta.arcgis.com with a fix to this issue, would you mind trying on the beta website to see if it works for you? The fix will be applied to the Survey123 website https://survey123.arcgis.com late this week. Thanks, Zhifang ... View more

Hi Jamie Till‌, Would you mind letting the user use a double quotation instead of a single quotation in the template? For example, ${if signage_place_com_type=="comment"} We stopped supporting the single quotation in a report template since 3.4 release, it would be a little strange if the template could work before the 7/2 release of the website. Otherwise, can you please share the XLSForm and the template so we can look into the issue? Thanks, Zhifang ... View more

Hi Christopher Van de Wyngard‌, Would you mind sharing us a screenshot after clicking the "Show details" link button and also together with the Recent tasks panel expanded? Or a Job ID of your failed task would also help. Thanks, Zhifang ... View more

Hi EnelGreenPowerNA, Thanks for the additional information, this helps understand the issue. We're looking into this and will get back once we notice something. Thanks, Zhifang ... View more