I created a map for collecting data via Collector for ArcGIS (Version 18.1.0).
This map includes three editable layers (1x points, 1x lines and 1x polygons)
However, when I open this map in Collector for ArcGIS on the iPad (iOS 12) only one of these layers get loaded into the map. Which one seems to be randomly...
The error message I got is:
Description:The item to be created already exists in the database
The three layers were created via the AGOL collector template and have the same fields.
Solved! Go to Solution.
Thanks for your use cases and feedback! The October 2019 update to ArcGIS Online included a fix so that when editing domains in ArcGIS Online, domains are renamed for all hosted feature services, not just those created through ArcGIS Online. This means that the fix of editing the domains again to get them renamed will now work for feature services that were published through ArcGIS Pro.
Thanks again for your feedback and workflows, as it helped us to prioritize the work and get this fix pushed out.
Hi Marco! I'm going to guess that each of your layers has a field with the same name as the other layers, and that you created a list (of choices for data entry) for that field in each layer. Is that correct? This is a known issue that we are working on. For now, use different names for fields that have lists.
I as others are having this same issue: also see topic:
Too bad....renaming fields, like you said, would be a huge pain. Going to continue using Classic Collector.
Unfortunately, alias renaming doesn't fix this. Right now, you would have to rename the field itself. We are working on a fix (and existing data will also benefit from it) but the fix needs to go into ArcGIS Online and is expected to come with the next update to that site (in the March timeframe).
So this has nothing to do with my feature services being published to HTTP, and not HTTPS?
Also, the issue you outlined above refers to having more than one layer with the same name and domain values? How about subtypes? I have a layer with subtypes and domains applied to one field, could that be the issue?
If you are working with subtypes, my guess is that you are using either ArcMap or ArcGIS Pro to publish your data. If so, you can hit this error, but it comes about if you have a map with multiple layers coming from different geodatabases, and those geodatabases contain domains with the same name and different values, and you publish that map as a single service. Subtypes don't affect this.