In desktop you will see the sync option on the feature service capabilites (Add Update Delete Sync) or on AGOL when you go to the item page for that service and click edit you will see the sync option at the bottom of the page where you can enable editor tracking.Can you share the service with me an I can check it out.Russ
That is an ArcGIS Server service and not a hosted feature service. So the AGOL information will not be present on the feature service item page if you added the service to AGOL. The next thing I saw on the service is the editor tracking field CreatedBy. I took a look at the error coming back:{"error":{"code":400,"message":"Unable to complete operation.","details":["Invalid column value [CreatedBy]"]}} I am thinking this is happening because with editor tracking and the ArcGIS Server service is not secured which does not use the logged in name and it is trying to populate this field with esri_anonymous which is longer then the field you have set up allows. Maybe try to change the character length of the field and see if that works when you republish the service.CheersRuss
I've done the same. Will you please repost if it stops working again without warning? I am still having the problem where all of a sudden it just stops working in connected mode.
Your server is 10.11. Sync is only supported on 10.2.2 servers and up. You will need to upgrade your server to get the sync functionality working on your on-prem server.
Russ
We ran into a similar issue today; we have a feature layer setup for editing and we wanted to add the ability to support photo attachments. This should be a trivial task by enabling attachments through the AGOL UI. However when we tested this we got the "Update Failed 1 attachment could not be sent" error message. After hours of troubleshooting I finally googled the error message and it lead me here. Republishing the service seemed like a solution for some. As we investigated this we noticed that Extent, within the rest end point, had a mixture of lat/long and state plane coordinate values. Leading us to believe that the data got corrupted somehow. We had other issues when trying to export the data but we were finally able to export it. We now host the data in our Portal so we have better control over it. But in the end we did have to republish the service and everything is working as expected. I hope this helps someone.
I'm convinced SDE has a lot of problems, either that or somehow AGOL is corrupting my services. There seems to be no rhyme or reason why a service suddenly becomes corrupted and the other solution seems to be (from Support) to export the offending features class(es) to a file geodatabase and import them back in. And, of course, Collector uses AGOL to function.
We had similar issue and found that our SDE database was locked out by a 'compress/index SDE' scheduled task. After terminating the hanging task, the SDE database was fine to accept user data submissions.
I have totally agree with Josh on his last post "SDE does seem to have lot of problems".. after a some of testing myself.
I have never run into these issues when publishing "hosted services" for use in Collector.
If this helps someone out there...
I have been struggling with this un-informative message for weeks. I have archiving enabled (because I can't get versioning to work in offline mode), ArcGIS Server 10.2.2 and a web map on ArcGIS Online.
Users:
After a process of elimination (on a 1.2 million record feature class) I discovered that the GlobalIDs had an issue. I deleted the GlobalID field and recreated it. It now works OK....well until the next Collector challenge!
Signed in members can post, follow updates, and more. New here? Register a free account.
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.