I have a question about Survey123 submitting data to an ArcSDE geodatabase feature class, specifically about this article regarding publishing the feature layer with supportsApplyEditsWithGloablIDs to allow for this: https://community.esri.com/groups/survey123/blog/2018/07/17/how-to-turn-supportsapplyeditswithgloabl...
We have an existing survey tied to a feature class that now requires versioned functionality. I’ve done some testing and it appears that after publishing the feature layer in accordance with the steps in the above article, that submissions still work when I disable archiving in the geodatabase, disable sync in the related feature layer, and enable versioning in the geodatabase feature class. However, this is contrary to what is stated in the article.
Do you know if this is still a limitation of Survey123 (V.3.3.51)? If so, I would imagine there is risk involved in adjusting our production data to this configuration despite seemingly normal behaviour, correct?
These are the steps I followed where the outcome is still a seemingly functional survey:
- Enable archiving on feature class in the geodatabase
- Publish feature layer with sync enabled
- Create and publish a Survey123 based on the feature class published in step 2
- Test Survey123 (result = records successfully submit)
- Stop services for feature layer published in step 2
- Disable archiving in the geodatabase for the feature layer
- Enable versioning for feature class in the geodatabase
- Change feature service properties in ArcMap to disable sync and start service
- Submit record through survey123 published in step 3
- Check database feature class (result = record successfully submitted)
I also replicated the survey in Survey123 Classic and the submission behaviour is the same as the current version of Survey123.
