topic Re: Not all layers get loaded in Collector for ArcGIS in ArcGIS Collector Questions

Not all layers get loaded in Collector for ArcGIS

MarcoPoetsch_ret — Tue, 11 Dec 2018 03:48:28 GMT

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.

Re: Not all layers get loaded in Collector for ArcGIS

Kylie — Tue, 11 Dec 2018 15:59:24 GMT

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.

Re: Not all layers get loaded in Collector for ArcGIS

MarcoPoetsch_ret — Tue, 11 Dec 2018 19:03:21 GMT

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

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

Re: Not all layers get loaded in Collector for ArcGIS

TravisSmith1 — Tue, 11 Dec 2018 21:28:44 GMT

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=818821#comment-818821

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

Re: Not all layers get loaded in Collector for ArcGIS

TravisSmith1 — Tue, 11 Dec 2018 21:41:44 GMT

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.

Re: Not all layers get loaded in Collector for ArcGIS

GeneSipes1 — Thu, 13 Dec 2018 14:43:56 GMT

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

Re: Not all layers get loaded in Collector for ArcGIS

Kylie — Wed, 16 Jan 2019 19:04:50 GMT

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

Re: Not all layers get loaded in Collector for ArcGIS

Kylie — Wed, 16 Jan 2019 19:20:18 GMT

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.

Re: Not all layers get loaded in Collector for ArcGIS

RobBlash — Fri, 01 Mar 2019 20:26:34 GMT

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

Re: Not all layers get loaded in Collector for ArcGIS

RobBlash — Thu, 07 Mar 2019 00:20:40 GMT

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

Re: Not all layers get loaded in Collector for ArcGIS

Kylie — Thu, 07 Mar 2019 20:39:59 GMT

This fix will be part of the next ArcGIS Online update (not Collector). That should be around March 19th. Be aware that for existing layers with the problem, you will need to edit the layer to get the fix.

Re: Not all layers get loaded in Collector for ArcGIS

RobBlash — Thu, 07 Mar 2019 20:57:25 GMT

Ok thanks for the info. Incidentally I crated a new map and everything now works as expected in the latest Collector update. Previously I was seeing the "Code=3054 "The item to be created already exists in the database."" error for some layers.

Are there multiple causes for this issue? I did re-publish some data that went into the new map, but there were no significant schema changes.

Re: Not all layers get loaded in Collector for ArcGIS

Kylie — Fri, 08 Mar 2019 23:48:36 GMT

Yes, there have been a couple of reasons we've seen that error.

Re: Not all layers get loaded in Collector for ArcGIS

ScottKiley — Wed, 20 Mar 2019 13:47:06 GMT

I am still experiencing this problem with the new version of Collector after the update. I'm wondering if anyone else is as well.

Re: Not all layers get loaded in Collector for ArcGIS

Anonymous User — Wed, 20 Mar 2019 15:16:01 GMT

We are experiencing the issue with both versions of collector this morning...

Re: Not all layers get loaded in Collector for ArcGIS

Kylie — Thu, 21 Mar 2019 17:00:28 GMT

If your layers were created in ArcGIS Online, they have updated with a fix to the issue. Newly created layers won't see this problem. To take advantage of it in your existing layers, you need to edit the list in the Item Details page and resave it. It can be as simple of an edit as removing a space and putting it back and clicking 'Save'. The underlying issue was duplicated names for the lists, and when they are resaved they'll get renamed and use a new, unique naming convention.

Re: Not all layers get loaded in Collector for ArcGIS

ScottKiley — Thu, 21 Mar 2019 18:35:11 GMT

I've made changes as you described to all fields with domains in all layers in the hosted feature layer with data not loading into Collector and the problem still happens. The hosted feature layer only has 2 feature classes. Neither of them have matching field names nor do they have matching domains. For some reason one of the layers loads into Collector, but the other fails.

I submitted a support request as I may be experiencing a different issue, but I am still getting the error below:

Domain: com.esri.arcgis.runtime.error
Code: 3054
Description: The item to be created already exists in the database.

Re: Not all layers get loaded in Collector for ArcGIS

Kylie — Thu, 21 Mar 2019 18:42:38 GMT

A support request is the right path forward. We have seen this for some different reasons, and you might be hitting one of those, and not the one that was fixed. Thanks!

Re: Not all layers get loaded in Collector for ArcGIS

RobBlash — Mon, 25 Mar 2019 09:50:48 GMT

When I was experiencing the issue creating a brand new web map helped to resolve it.

Re: Not all layers get loaded in Collector for ArcGIS

EricPescatore2 — Wed, 27 Mar 2019 14:28:52 GMT

Good afternoon may as well add another Project to the pile. A feature layer published a little under a year ago has stopped working in the New Version of Collector with the ERROR: 3054. This seems to have occurred with either update to AGOL. As of yesterday 3/26/2019 there we no problems and now we are encountering issues.

I am not entirely sure and will need to re-read this thread as to the FIX. But republishing the feature service may not be an option for us. It does seem that Classic Collector works fine with the Dataset, but if this error is related to "New" Collector. This is quite unfortunate.

Even creating a new empty MAP results with the same error with the affected feature service.

Is the best bet to open a TICKET with ESRI and use business partner credits to get a direct line?