Latest Contributions by ZhifangWang

Hi Melissa, If your survey does not have a repeat, the individual response view in the Data tab of the Survey123 website would be a nice option to edit data. We introduced this capability in the 3.4 release https://community.esri.com/groups/survey123/blog/2019/05/24/comet-halley-update-may-23-2019 and enhanced it in the just-released 3.5 version https://community.esri.com/groups/survey123/blog/2019/06/28/world-ufo-day-release-35 so that users other than the survey owner can also edit their own records in the same way. This could save the user from composing the URL to open the web app directly and have appropriate privilege control (only their own records).  Hope this helps. ... View more

Hi Nicholas, The editing workflow by non-owner users on the Data page of the website has been enhanced in the upcoming 3.5 release, where you can directly control what submitters can do (Add only, Add and update, or Add, update and delete) in the website UI. As long as the user can view the Data page (as a viewer) and also have the appropriate privilege (as a submitter, Add and update at least), he should be able to update the data in the website UI. Does this make sense to your workflow? ... View more

Hi John, Thanks for the information, which is helpful for designing the workflow. I'll also log it in our backlog too. Thanks, Zhifang ... View more

Hi Christian, Thanks for the update. Based on the latest information you provide, I assume it to be the cache issue we mentioned earlier: the other user will see the number correctly at the first time of signing in no matter how many records are there, however, the number seems to be cached from then no matter clearing the browser cache or sign out/sign in again. This bug will be fixed by ArcGIS Online in the next release, planned just before the UC. Will let you know once the fix is available. Thanks, Zhifang ... View more

Hi Christian, Thank you for the test and the above information. From the current screenshots, seems it's not the cache issue I mentioned above since in the chart of the Analyze page, your colleague's account (other than the owner) still cannot see all records regardless the count in the lower right corner. For the loading error in the Data page, can you please try to open it in the incognito mode of the browser (such as Chrome) or clear the browser cache before opening to see if it can be reproduced every time? Also by looking into the screenshots, seems the records your colleague's account can see just equals the records count submitted by anonymous users show in the Overview page (first screenshot). Would you mind trying to submit two more records, one by the owner (need logged in) one by an anonymous user? Then observe how many or what records can your colleague's account see in the Analyze/Data page. If the new added record submitted by the anonymous user can be observed but the owner's one cannot, seems you need to check the option in Collaborate->Viewer tab to ensure "All records in this survey" is checked under "What data can viewers see?". ... View more

Hi John, Thanks for raising the question. Currently, the entire .csv file used by pulldata is shared together with the form item, so it means anyone can access the survey (form item) can download/get the .csv file technically, either through the web app or the field app. I will raise your concern to the team for discussion to see if we can come with an enhancement. Before that, I would like to check with your use case, do you want to restrict the logged in user only can access the records submitted by themselves in a previous survey? Or the logged in user can also access other records submitted in the previous survey by other users, or even the survey will be shared with the public but you still do not want to share the .csv data with anonymous users. The first scenario may make sense from the implementation perspective but the latter two will be hard or even impossible. Thanks, Zhifang ... View more

Hi Christian, Can you please confirm if it's only the records count is not incorrect but the users other than the owner can still see all the actual records in the Data or Analyze tab? For example, if you sign in Survey123 website as a stakeholder in the group for analysis, in the Data tab, can you see all expected records in the feature table or all records in any chart of the Analyze tab regardless the total number? We have a known caching issue with ArcGIS Online as mentioned by James, but if this is not your case, we would like to know more about the details of your situation. Thanks, Zhifang ... View more

Hi Anne,  Thanks for the information. I think you encountered one known issue in our backlog: once the survey is shared with other viewers on Survey123 website, you cannot re-publish the survey in Survey123 Connect (or you need to delete the _stakeholder feature service view item manually before re-publishing). I've logged your voice in our backlog. Thanks, Zhifang ... View more

Hi Anne,  Sorry for the inconvenience.  Just want to double check, when you said "make major changes that wipes the data from the survey", do you mean to make schema changes to fields in the survey layer or just delete features/records in that layer? If it's the first case, the stakeholder view is supposed to updated automatically as long as you do the changes within the Survey123 website, would you mind sharing some detailed steps for us to reproduce the issue? Thanks, Zhifang ... View more

Hi Erica, Just FYI, from the next 3.4 release, when referencing the field of a parent layer inside a repeat, if there are any special characters in the layer name, please use underscore to replace them.  For example, the parent layer name is "this-is a parent.layer", then use "${this_is_a_parent_layer.field1}" inside the repeat. This does not affect any existing report template which does not encounter the issue that the layer name contains special characters. ... View more

Hi Mike, For example, you have the following survey schema, mainLayer   |--repeat1     |--repeat2       |--repeat3 you can use the  ${layerName.fieldName}  syntax to access questions in parent layers. Note: you have to traverse each parent repeat before opening a child repeat, otherwise, the current parsing scope does not know which repeat instance to be used as the context. ${#repeat1} ${#repeat2} ${#repeat3} ${field1InRepeat3}, ${repeat2.field1}, ${repeat1.field1}, ${mainLayer.field1} ${/repeat3} ${/repeat2} ${/repeat1} ... View more

Hi Zach, Thanks for sharing the template with us. Actually, the "propertyname" should work in the template. If you check the header of the second page in the report template, there's a placeholder ${propetyname} which has a typo (missing an "r"). The "propertyname" issue will be gone once you fix this typo. Thanks, Zhifang ... View more

Hi Amanda, Great! Please don't hesitate to let us know if you have any other question or feedback. ... View more