Hello,
I have a Collector user out in the field using an offline web map featuring an ArcGIS online hosted feature class. He has been using this successfully but is now getting the following error messages "Abort due to constraint violation" and "Unable to open the database file - Create virtual table for selection failed" when he tries to collect a point. It seems to be intermittent. It is now allowing him to collect a point but not delete a point. I have not been able to replicate the error with his login on my device. He has tried to remove the map from his device and download again and it has not solved the problem.
One of my field staff has also received this error but my other staff in the same area has not. I worked again only after removing and downloading the map again. Would have been annoying if there was no cellular service.
Has anyone found a resolution to this? One of my field inspectors received this error for the first time today - they have been using the same application for nearly 9 months with no changes to the schema or layer.
I'm receiving the error: "Unable to Submit -Abort due to constraint violation"
I just set up a map for collector using the ArcGIS Blog titled "Make your first Collector map". I went out and collected a few features and came back in to check the results. Everything worked as planned. I went back out and collected a path - worked well. Finally I attempted to collect an area (the building perimeter) and after pressing the "Submit" button I received the error.
I know this isn't the exact issue everyone else is having but hopefully it will help someone somewhere.
EDIT: As you can see, I'm using the new Collector app for iOS.
Also not happening on our iOS devices using the new Collector. Hoping the issue silently goes away when the beta evolves to the real deal. And soon would be better.
Any ideas ESRI when the beta will turn?
I agree with you Ronald... intermittent and non-reproducible errors are the toughest to crack. This error has been popping up on us on different Android devices and different versions of Collector Classic. We've yet to see it in the iOS version. It is pretty frustrating since it can make a scheduled day of field work almost wasted. Hoping that someone figures it out or future updates fix it. Thanks for sharing your pain.
I guess my biggest concern, well over being restricted in field use, is that it is not a consistent error and cannot be re-created for analysis. I have no idea what could be causing this in the geodatabase. I believe that it stems from some Collector vs. OS issue more than anything else.
We have another error when downloading maps in Collector Classic for Android. ESRI has that case but have never found any corrections. We started downloading smaller area maps with far less detail and have not had the issue re-occur since. Still waiting on the new Android Collector to get out of beta status so we can utilize the functionality of the offline map areas, but I digress as that is another story.
Good luck Jimmy!
We have experienced this same issue and have been unable to figure out why as well. This issue appears to surface randomly and only affects certain editable features in the web map. Other features can still be created.
I've looked at the .geodatabase files and nothing jumps out at me.
You'd think a constraint violation would have something to do with a unique primary key, but that doesn't seem to be the case here. I've also tried to find a way to turn on logging in Collector, but haven't found anything.
We have just experienced the same issue. I checked the fields and domains in Pro by opening the AGOL web map that contains the features being collected. Nulls are allowed and this is the typical setting when creating the features in Pro then uploading as a hosted feature. The online table has the value "empty" that is the default if nothing is selected in the field from the associated initial domain values. The online field details look like this;
In the hosted feature layer were any changes made to the fields and domains? This error has popped up before when fields were allowed to be populated with 0 characters, but domains were set that were greater than 0 characters. Try checking the fields and domains.
I also have this issue with one of my students and their phone, "Abort due to constraint violation". ESRI Collector started working just fine he then alter the setting to enable averaging, and after that could no longer collect features. He would get the same error each time, "Abort due to constraint violation".
Les membres connectés peuvent publier, suivre les mises à jour, et plus encore. Nouveau ici ? Inscrivez-vous gratuitement.
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.
