Latest Contributions by ZhifangWang

Hi John Donoghue‌, Can you please share in which browser and the version you observed the UTF-8 prefix issue? If it's not Chrome, would you mind trying Chrome to see if the issue still exists? ... View more

Hi tim dunlevie‌, Thanks for the reaching to us. I can see this is interesting leverage of the filter in the website UI in the report, which makes sense. However, this is not available currently, I've logged an enhancement issue in our backlog. Please feel free to raise an issue to Esri Support Service to add priority to this enhancement. For now, the workaround is to update the report template manually as needed. In the meantime, we need to figure out how to extract a variable value from the filter, since the filter set in the website UI could be from simple to complex, although the entire filter will pass to the report engine, it would be hard to parse a portion if the filter is complex. Thanks, Zhifang ... View more

Hi Laura, As we just rolled out an update in EAC for the Survey123 beta website, it includes a potential fix to this issue. Can you please help try to see if this fix works for you? Thanks, Zhifang ... View more

Hi RAB Consultants‌, Currently, it is not possible to apply a filter a web map that is used in a geopoint/map question in the feature report. For example, if the surveyor worked on a property A and had 10 measurements around the property, e.g. 1,2,3,4,5... can you please confirm that your requirement is to print a map that only includes the 10 measurements (but not includes any measurements for other properties) in the feature report? ... View more

Hi Rob Cahalan‌, Would you mind sharing a copy of the XLSForm file and the report template file to zwang at esri.com so we can try to reproduce the issue? You can just leave necessary questions in those files as long as they can be used to reproduce the issue.  ... View more

Hi Julie Barrett‌, If you use the Survey123 web app, I think this could be done technically somehow by using https://community.esri.com/groups/survey123/blog/2020/03/05/introducing-the-survey123-web-app-javascript-api . For example, For every question in your survey, set up a onQuestionValueChanged event. In this event, you will manually send data to the behind feature layer. Also, you are responsible to check if there is already a feature in the feature layer for this survey session, if no, created a new feature, if yes, just edit the existing feature for this survey session. Disable the default submission action (to the feature service) by using isDisabledSubmitToFeatureService in the JavaScript API to prevent duplicated records. I also logged necessary support for this workflow in our backlog, for example, hide the submit button. In the meantime, it's no harm for you to submit an enhancement request to Esri Support Service to prioritize this workflow. Thanks, Zhifang ... View more

Hi Yulia Mamonova‌, Can you please share some details of your use case? For example, by the meaning of "the group is empty", do you mean all questions in the group do not have an answer? In addition, what do you want to output for the group if it's not empty? ... View more

Hi GISAdmin GKB‌, Thanks for the sharing, glad to hear the new summary/statistics capabilities work for you (to some extent). By design, if you do statistics or iteration for records in both the survey main layer and its related layers (repeat in Survey123) in a summary section, you need to use the '| where:""' filter to control what records to be included in the stats/iteration. This is because there is no "default context" or you can consider the "default context" is all records in each layer ( '| where:"1=1"'). On the contrary, if you do statistics or iteration of records in a related layer/repeat in an individual section/individual report, there is a "default context": data range for related layer/repeat will be restricted to records that only related to the current record in the main layer. For example, in your individual report template, if the current record in the main layer is hydrantID=15, then the following: statistics: ${inspections | stats:"count,objectID"} iteration: ${#inspections}...${/} will only use inspection records that related to the hydrantID=15. Furthermore, if you need to do a stats for other records that are not related to hydrantID=15 in the current individual report, you can use the !important keyword to overwrite the current "context". For example: While the hydrantID=15 has ${inspections | stats:"count,objectID"} inspections, there are ${inspections | where:"hydrantID=16 !important" |  stats:"count,objectID"} inspections for the hydrantID=16. Hope this may help and please let us know if you have any question. Thanks, Zhifang ... View more

Hi Harmond Santos‌, Generally speaking, Survey123 submits data to a feature service. In your case, you may want to first publish your SQL Server database table as a feature service in ArcGIS Pro, and then create a survey from that feature service. Then data collected with this survey will be submitted to the underlying database table directly. For how to create a survey from an existing feature service, Use Survey123 with existing feature services—Survey123 for ArcGIS | Documentation  would help. ... View more

Hi Hussam Rabea‌, Thanks for the feedback. I saw there is a similar issue here https://community.esri.com/message/934689-an-error-while-generating-feature-report-portal-for-arcgis , if this is the same problem, maybe we can continue discussion there so any other user who has the same issue has more chance to see it. ... View more

Hi Hussam Rabea‌, As we had an update for the website on 7/2 and also planned some fixes for the production website soon, would you mind trying to see if you can still reproduce the issue on the latest Beta website https://survey123beta.arcgis.com?portalUrl=<your portal> ? ... View more

Hi Aurelija Ruta Viluckyte‌, The fix to the issue is available on our Beta website https://survey123beta.arcgis.com now, would you mind trying to see if this works for you? If it works well, we plan to deploy the fix to the Production website later this week. ... View more

dan becker‌, Yes, the workaround is on the Beta website now (planned later this week for the Production website), thanks for the confirmation.  ... View more

Hi ALL, We are working on a workaround in Survey123 to bypass the issue in ArcGIS Enterprise 10.8. 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. Please see https://community.esri.com/thread/256233-survey123-feature-report-anticipated-fix#comment-940052 for details. Thank dan becker‌ for the information. ... View more