1. I created a survey for staff to collect field data, WaterTyping v2.
2. I published this survey.
3. I created a new survey for staff to edit the collected field data WaterTyping Web Edists v2 using the Feature Services, and selecting the hosted feature layer WaterTyping v2.
4. I made some small changes needed for the editing process.
5. I attempted to publish the new survey and I am getting this error.
The custom feature service submisssion_url is not compatible with the survey.
Fields not found in feature service: 0
If anyone has experience trouble shooting this error please let me know.
Much thanks!
Aaron
If you use a submission URL Connect can then no longer add any fields to the service. So you will need to add those fields manually through AGOL so that the schema of the form and the service match.
When you were first publishing and not using a submission URL you did not see this since at that point Connect was still controlling the service. But now it is not so you have to make the two match on your own.
Hope that makes sense. There are a few posts on this I think you could look at for more info. One is https://community.esri.com/t5/arcgis-survey123-questions/feature-service-submission-url-not-compatib...
Doug,
Thank you for the reply!
I have diligently worked through both tables to make sure a new field was not added, and I have confirmed that it was not.
Is it possible that there is another reason I am getting the error? Thank you for your help.
Aaron
Did you enable attachments, add editor tracking, change a data type, or change a text field size?
Like posted below one way to troubleshoot is publish a totally new temp form from the current form xlxs using the File option in Connect. Then go into AGOL and download this new service as a GDB. Then compare that to your current service. That should help you find it.
You can turn on logging to see more information about what field is causing issues. Click on your profile and go to settings. Move to the diagnostics tab and toggle on logging. Try and republish and then go to the log file.
I'm also curious as to what version of Connect you are using, as the newer version provides more info in the publishing error.
Thank you Jen!