You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
You have to go to these feature layers and make this specific change to editing so that more than just the person who entered the Survey can make updates. 9794a7 SARCOP v9 Team Fact Sheet Editable View (arcgis.com) - this one seems to repeatedly set itself back to only allowing editors to edit their own features.
Priority impact
p0 - not time sensitive
Impact
When this happens unexpectedly, suddenly users cannot edit existing surveys unless they use the exact same login.
The text was updated successfully, but these errors were encountered:
Which app?
Other
Describe the Device, Operating System, and Browser
Windows, Any browser, Web Form Survey123
Describe the bug
The feature layer editing settings get reset anytime you edit the settings within the Survey123 Collaborate Page or make edits to the Design.
Expected Behavior
We'd expect the settings to persist.
Reproduction Steps & Sample
Setup sharing on your editable feature layer as shown
Go to Survey123 Web Designer
Make any change to the design of the survey OR sharing permissions under Collaborate
Go the edit permissions on your editable view for that Survey123 Form - you will see they have reset to Editors can only edit their own features
Other Relevant Info
Workaround
Whenever you make a change in Survey123 Web Designer
https://survey123.arcgis.com/surveys/f0c2ab27da8f49e6bf98d28926b416a0/design
You have to go to these feature layers and make this specific change to editing so that more than just the person who entered the Survey can make updates.
9794a7 SARCOP v9 Team Fact Sheet Editable View (arcgis.com) - this one seems to repeatedly set itself back to only allowing editors to edit their own features.
Priority impact
p0 - not time sensitive
Impact
When this happens unexpectedly, suddenly users cannot edit existing surveys unless they use the exact same login.
The text was updated successfully, but these errors were encountered: