Hi Travis,
Thank you for sharing that information. With regards to the error you're seeing in Collector 18.1.0, 'The item to be created already exists in the database.' this is a known issue that is still being investigated on our end.
The underlying problem, from all the cases we've seen up to this point, deals with coded value domains having the same names but containing different values.
For example, you have a feature service with three layers in it, all of which have a field called 'Type'. Lists/domains are created for each 'Type' field for each layer in the service. Layer 1 has types 1-3, layer 2 has types 4-6, and layer 3 has types 7-9. When the subsequent map is opened in Collector, only the first layer will load, the other two layers will fail to load in the map and displays that same error in the 'Layers' list. Collector is 'seeing' duplicate domains with different values because when a list is generated through ArcGIS Online, as they were in this example, the field name is used as the domain name.
In the example I provided above, this happened across multiple layers in the same service. Individual services with single layers are fine.
This issue can also happen if you have duplicate domains in the same layer as oppose to separate layers in the same service.
Would you be able to share with me a map(s) that can reproduce that error? If so, please add them to a new group and invite the Collector4ArcGIS user into that group.
Here are a few potential workarounds. Since the main issue is that the domains have the same name but different values, essentially they need to be made to match or have different names:
- the domains need to include the same exact values.(Using the example above, would mean the list/domain would include values 1-9)
- the domain names need to be changed, which as in the case of hosted feature services would entail having to create new fields and applying the same domain as before. The values would not need to match in this case because the names would be unique. (Using the example above would mean having fields called Type_A, Type_B, Type_C that contain the same unique values as they do currently.)
Therefore this issue happens regardless if you perform a download or not. The download is just failing due to this issue. The download itself isn't the problem.
Regarding the other issue with why you can no longer download in Collector Classic, just for clarification, this issue only happened starting today, but was working correctly? For the previously downloadable maps, in AGOL in the web map settings page, are they still offline-enabled? Are the feature services still sync enabled? But the download icon is no longer available for those maps in Collector Classic? Can you share one of these maps as well?
Thank you.
-Kevin