Not all layers get loaded in Collector for ArcGIS

8512
43
Jump to solution
12-10-2018 07:48 PM
MarcoPoetsch_ret
New Contributor III

Hi all,

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:

Domain: com.esri.arcgis.runtime.error

Code: 3054

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.

Tags (2)
1 Solution

Accepted Solutions
Kylie
by Esri Regular Contributor
Esri Regular Contributor

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.

View solution in original post

43 Replies
Kylie
by Esri Regular Contributor
Esri Regular Contributor

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.

MarcoPoetsch_ret
New Contributor III

Oh, I thought that's the issue...

Is there no other workaround as renaming the fields?
That would be a pain.

0 Kudos
TravisSmith1
New Contributor III

I as others are having this same issue: also see topic:

https://community.esri.com/message/818821-re-map-download-failed-with-new-1810-version?commentID=818... 

Too bad....renaming fields, like you said, would be a huge pain. Going to continue using Classic Collector.

0 Kudos
TravisSmith1
New Contributor III

Wait...could I change the field alias name and have that work? Or do I have to change the actual field name (which is a pain). Thanks.

0 Kudos
Kylie
by Esri Regular Contributor
Esri Regular Contributor

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).

0 Kudos
RobBlash
Regular Contributor

Hi Kylie Donia‌, is this fix still scheduled for the next update? Any word on when that might be?

0 Kudos
GeneSipes1
New Contributor III

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?

Thanks

0 Kudos
Kylie
by Esri Regular Contributor
Esri Regular Contributor

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.

0 Kudos
RobBlash
Regular Contributor

Kylie Donia‌ was this intended to be fixed with the v19.0.1 Release? I am still getting this error after the app update.

0 Kudos