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:
I also replicated the survey in Survey123 Classic and the submission behaviour is the same as the current version of Survey123.
Given that Survey123 only checks the state of the feature service when publishing a form, Survey123 is unaware of the changes that you made after that point in time in your process. Could you check if 'supportsApplyEditsWithGlobalIds' is true at the feature service level? Survey123 relies on this being true to successfully submit information. If this is not true, we cannot make any warranties regarding the security of the data transfer. In particular, I would expect issues to possibly arise around the cases where a related record did not successfully submit and likely around editing workflows.
Is there a way to create a survey with versioned enterprise data? Is that something that is being worked on? Don't want to change everything around and then next release addresses it....