Latest Contributions by Ruth_JiatengXu

Hi Srini, Yes, you can import your custom report template into Survey123 using the new template button. The provided sample template can be used as the base of your custom template, and you can also use the new Quick reference page as a syntax reference of the report. The report is a pretty powerful tool, and here is a blog introducing the report functionality which is worth reading https://community.esri.com/groups/survey123/blog/2019/07/23/understanding-survey123-feature-reports. Thanks, Ruth ... View more

Hi Jennie, This might be a different issue. Could you please let us know which is the survey published version, and which is the version they used to render the survey? If it is possible could you please also share the XLSform with us [email protected], so we can diagnose the cause of this issue? Thanks, Ruth ... View more

Hi all, Fiona Barry‌ Fco Javier Romero‌ Matt Mulder‌ Jennie Catalano‌ Thanks for the help, the fix is now available for testing on our BETA website https://survey123beta.arcgis.com/, if the hotfix build passes the test, we will then deploy the fix on the production website next week.   Thanks, Ruth ... View more

Hi Yulia and Shawn, The fix is available for testing on our BETA website https://survey123beta.arcgis.com/, and if the hotfix build passes the test, we will then deploy the fix on the production website next week.   Thanks, Ruth ... View more

Hi Matt, Thanks for the help and waiting. The hotfix build is now on our Beta website https://survey123beta.arcgis.com/, you could test the fix on the BETA website. If the hotfix build passes the test, we will then deploy the fix on the production website next week. Thanks, Ruth ... View more

Hi Yulia, Sorry for the inconvenience, this issue will be fixed in the upcoming hotfix soon. Thanks, Ruth ... View more

Thanks a lot, Paul, that is very helpful! We are still evaluating the proper timeline to roll out the hotfix, in the meanwhile, I encourage you to contact Esri Support to raise a bug, which helps us assess the impact of the issue and prioritize it accordingly. I will reply to this post when the fix is available. Thanks, Ruth ... View more

Hi all, Thanks all for raising the issue, we are sorry for the inconvenience. With the info provided by Matt, we are able to identify the cause for this issue now, and we will have this fixed in the upcoming hotfix. If it is possible, could you please share your XLSForm that leads to this error? Then, we can test the fix more thoroughly. If you are not able to provide the form, could you please let us know is there an external choice question included in your survey? Thanks, Ruth ... View more

Hi Jussi, Survey123 web app currently does not support projected coordinates in the URL, so the (x,y,WKID) method mentioned in the ArcGIS Online Doc does not work for the web app. For the current web app version, we only support the geographic coordinates in the URL, and it can take(x,y) for the 2D point or (x,y,z) for the 3D point, that is why in your example the 4326 becomes elevation. Thanks, Ruth ... View more

Hi Matt, Thanks for your quick response, and we are sorry for the inconvenience. We have identified the cause of this issue, and we will have this issue fixed in the upcoming hotfix. I will respond to your post when the fix is ready. If it is possible could you please provide one of your XLSform for us to test the fix?  Thanks a lot! Ruth ... View more

Hi Chris, The Geoshape value is now supported in the web app URL field:fieldname=. Please see the note in the Parameters for web app section in this documentation: Integrate with other apps—ArcGIS Survey123 | Documentation.  Thanks, Ruth ... View more

Hi Matt, We are looking into this issue, if it is possible could you please let us know the job ID of the failed job? Thanks, Ruth ... View more

Hi Jennifer, I am so sorry that I missed your reply. I think editing the related table may cause the issue you encountered. I have created a survey with two repeats and another survey reference to the first repeat. With the settings mentioned above, I use the ?mode=edit&globalId=0b6bf520-8090-4b46-8952-c2c57f90782c (highlight in the screenshot below), then the survey can be loaded without error. However, if I use the parent global ID of the main layer, the error raised in the app. Another thing you could check is the form_id in the settings tab of your XLSForm, since if you are editing the related table, the error should be "can not edit layer '1-5'" instead of "can not edit layer '0'". Here are the settings I have, I put the repeatName as the form_id. Hope this is helpful, I will keep my eye on your post closely. If you have any other issues, please feel free to reply. I will try to get back to you ASAP. Thanks, Ruth ... View more

Hi Dongliang, Sorry for the late reply. Since you have the setting "what data can viewers see? Only their own submitted record", the non-owner user will only be able to edit the record that submitted by themselves.  If this was the case, could you please double-check the account and the record that you used for testing? Thanks, Ruth ... View more

Hi Zahrah,   Thanks for the information. I am wondering if the web app working properly to prevent blank required submission?    For the feature layer on ArcGIS online, the required question has the setting nullable:"true" by-design, this is because sometimes the required question is used as a relevant question, and when it is not relevant, the required question should be hidden and allowed to submit as null.   Could you please let us know your use case for having the feature layer field as nullable:"false", so we can log your requirement as a feature requirement. I also encourage you to contact Esri Support and raise an Enhancement issue.   Thanks, Ruth ... View more