AnsweredAssumed Answered

Not all layers get loaded in Collector for ArcGIS

Question asked by Badeschlapfen on Dec 10, 2018
Latest reply on May 14, 2019 by bmcelroy_hrc_engr

Like • Show 2 Likes2
Comment • 43

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.

9 people also have this question

Outcomes

43 Replies

KDonia-esristaff Dec 11, 2018 7:59 AM
Mark Correct
Correct Answer
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.
2 people found this helpful
Like • Show 1 Like1
Actions
- Badeschlapfen @ KDonia-esristaff on Dec 11, 2018 11:03 AM
  Mark Correct
  Correct Answer
  Oh, I thought that's the issue...
  
  Is there no other workaround as renaming the fields?
  That would be a pain.
  Like • Show 0 Likes0
  Actions
- trav2812 @ KDonia-esristaff on Dec 11, 2018 1:28 PM
  Mark Correct
  Correct Answer
  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.
  Like • Show 0 Likes0
  Actions
- trav2812 @ KDonia-esristaff on Dec 11, 2018 1:41 PM
  Mark Correct
  Correct Answer
  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.
  Like • Show 0 Likes0
  Actions
  - KDonia-esristaff @ trav2812 on Jan 16, 2019 11:04 AM
    Mark Correct
    Correct Answer
    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).
    Like • Show 0 Likes0
    Actions
    - rblash @ KDonia-esristaff on Mar 1, 2019 12:26 PM
      Mark Correct
      Correct Answer
      Hi Kylie Donia, is this fix still scheduled for the next update? Any word on when that might be?
      Like • Show 0 Likes0
      Actions
- gsipes @ KDonia-esristaff on Dec 13, 2018 6:43 AM
  Mark Correct
  Correct Answer
  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
  Like • Show 0 Likes0
  Actions
  - KDonia-esristaff @ gsipes on Jan 16, 2019 11:20 AM
    Mark Correct
    Correct Answer
    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.
    Like • Show 0 Likes0
    Actions
rblash Mar 6, 2019 4:20 PM
Mark Correct
Correct Answer
Kylie Donia was this intended to be fixed with the v19.0.1 Release? I am still getting this error after the app update.
Like • Show 0 Likes0
Actions
- KDonia-esristaff @ rblash on Mar 7, 2019 12:39 PM
  Mark Correct
  Correct Answer
  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.
  Like • Show 1 Like1
  Actions
  - rblash @ KDonia-esristaff on Mar 7, 2019 12:58 PM
    Mark Correct
    Correct Answer
    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.
    Like • Show 0 Likes0
    Actions
    - KDonia-esristaff @ rblash on Mar 8, 2019 3:48 PM
      Mark Correct
      Correct Answer
      Yes, there have been a couple of reasons we've seen that error.
      Like • Show 0 Likes0
      Actions
  - skiley @ KDonia-esristaff on Mar 20, 2019 6:47 AM
    Mark Correct
    Correct Answer
    I am still experiencing this problem with the new version of Collector after the update. I'm wondering if anyone else is as well.
    Like • Show 0 Likes0
    Actions
    - mbrueningesi @ skiley on Mar 20, 2019 8:16 AM
      Mark Correct
      Correct Answer
      We are experiencing the issue with both versions of collector this morning...
      Like • Show 0 Likes0
      Actions
    - KDonia-esristaff @ skiley on Mar 21, 2019 10:00 AM
      Mark Correct
      Correct Answer
      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.
      Like • Show 0 Likes0
      Actions
      - skiley @ KDonia-esristaff on Mar 21, 2019 11:35 AM
        Mark Correct
        Correct Answer
        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.
        Like • Show 0 Likes0
        Actions
        KDonia-esristaff @ skiley on Mar 21, 2019 11:42 AM
        Mark Correct
        Correct Answer
        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!
        Like • Show 0 Likes0
        Actions
        rblash @ skiley on Mar 25, 2019 2:50 AM
        Mark Correct
        Correct Answer
        When I was experiencing the issue creating a brand new web map helped to resolve it.
        Like • Show 0 Likes0
        Actions
        skiley @ skiley on May 7, 2019 6:58 AM
        Mark Correct
        Correct Answer
        While working with support they confirmed the the problem still persists after re-publishing the hosted feature layer and making a new web-map. My support analyst recreated the issue on his end.
        
        It lead to my issue being officially tied to BUG 00119563:
        All but one layer in a service fails to load in Collector for ArcGIS (iOS) when each layer contains a field with the same name and a Domain with the same name (but different list values). The following error message is returned: "Error Code 3054: The item to be created already exists in the database."
        Like • Show 0 Likes0
        Actions
      - cminteer @ KDonia-esristaff on Apr 11, 2019 10:26 AM
        Mark Correct
        Correct Answer
        "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'."
        
        Are you talking about editing the domain list for a hosted feature layer in the Data > Fields > FieldName > List of Values? Or are you talking about just making a change to one of the layer names in the Item Details page (I think that's what you mean.) How do you know the layer has been updated? Does the internal domain name for the field change (for example, when you look at the domain in ArcGIS Pro > Deploy ArcGIS Solutions Pro add-in > Modify Domains? Or does something else about the service change in such a way that Runtime / Collector knows about it and handles the "duplicate" domain names correctly?
        Like • Show 0 Likes0
        Actions
        KDonia-esristaff @ cminteer on Apr 16, 2019 12:51 PM
        Mark Correct
        Correct Answer
        Hi Chad - If you are seeing the error because you have different domains on fields of the same name, then you just need to edit the domain list for the layers. When the domains are resaved, their names are updated by ArcGIS Online and the names of the domains are then unique. This removes the problem since there are no longer domains with the same name and different values.
        1 person found this helpful
        Like • Show 1 Like1
        Actions
        cminteer @ KDonia-esristaff on Apr 16, 2019 12:58 PM
        Mark Correct
        Correct Answer
        Hi Kylie, thank you for your reply. So if I have for example TrapLocation, SampleLocation, LandingCountLocation all with a field called Priority, do I need to edit each of these domains to make the change? How can I verify that the names are updated by ArcGIS Online? The ArcGIS Pro AGO Deployment Tool plug-in shows the name of domains, but I think what it shows to users would not change, correct?
        Like • Show 0 Likes0
        Actions
        KDonia-esristaff @ cminteer on Apr 16, 2019 2:03 PM
        Mark Correct
        Correct Answer
        Yes, if those three domains have different values you'd want to edit each of them. Really you want to resave them (and to save requires a change). That will rename them (instead of just using the field name, ArcGIS Online now also uses other information to create unique names). I'm not versed in that tool and am not sure if it would show this or not. What shows to users doesn't change, it is the domain name in the underlying database that you are actually updating.
        Like • Show 0 Likes0
        Actions
        cminteer @ KDonia-esristaff on Apr 17, 2019 10:20 AM
        Mark Correct
        Correct Answer
        Sorry for all the follow-up questions... but, do I have to make the change to the Domain through ArcGIS Online front-end, or could I make the change through the REST admin endpoint? Reason I ask is that the affected data model in our case has 21 different fields that are duplicated at least once which have domains, across 39 different layers in the feature service, for 20 different deployments. The fact that we have to make an individual change on each list for each field in each layer on each service is incredibly time consuming and error prone.
        
        Any suggestions?
        Like • Show 0 Likes0
        Actions
        KDonia-esristaff @ cminteer on Apr 18, 2019 2:23 PM
        Mark Correct
        Correct Answer
        Hi Chad - I haven't tried it, and the recommended approach is to use the front-end as going through the REST admin endpoint can always introduce user-error But I've been told that it should work to go through the REST admin endpoint as the calls that need to be made to update the domain name behind-the-scenes should still get called in that case.
        Like • Show 0 Likes0
        Actions
        cminteer @ KDonia-esristaff on May 1, 2019 3:00 PM
        Mark Correct
        Correct Answer
        Hi Kylie, we aren't finding this method to work. For example, if I have ProposedTreatmentArea and Treatment both with a field called Method, I can create this error by changing the domain on one of them. If I edit the domain on both of those fields, I still get the error. Shouldn't editing the domain list through ArcGIS Online cause the domain to be resaved with a unique name so that this doesn't happen?
        Like • Show 0 Likes0
        Actions
        KDonia-esristaff @ cminteer on May 1, 2019 3:14 PM
        Mark Correct
        Correct Answer
        Hi Chad - Are you editing the domains while you have the map open in Collector? If so, please try closing and reopening the app. If that isn't what you're hitting here, could you specify for me what error you are seeing by changing the domain on one of them? Also, were these layers published through ArcGIS Online, or did you publish them using Pro or ArcMap? The fix only applies to layers created in ArcGIS Online.
        Like • Show 0 Likes0
        Actions
        cminteer @ KDonia-esristaff on May 1, 2019 3:22 PM
        Mark Correct
        Correct Answer
        Hi Kylie. No we don't have the map open in Collector. What we're seeing is that after changing the domain on one of these fields so that the domain lists do not match, we will get the error "Domain already exists". The layer was originally published from Pro to ArcGIS Online (Share As Web Layer). I wasn't aware that the fix would only apply to layers created in ArcGIS Online, I thought it would apply to feature services that are hosted in ArcGIS Online. So how can feature services that were published from Pro like that be fixed?
        Like • Show 0 Likes0
        Actions
        KDonia-esristaff @ cminteer on May 1, 2019 3:29 PM
        Mark Correct
        Correct Answer
        The update made to ArcGIS Online to change how naming is done is part of the creation process there, so it is limited to layers created there. You can fix this for layers created through Pro, but the fix is a bit different. Correct me if this isn't the case for you, but I'm guessing you have two layers in different geodatabases that you published as a single service in ArcGIS Online? For example, you made a map that had the two layers in it and published the map as a service. You have two ways to fix it in that case:
        Update the names of the domains in the geodatabases so that they are unique.
        Publish each feature class to ArcGIS Online separately, creating a separate hosted feature layer from each one.
        1 person found this helpful
        Like • Show 0 Likes0
        Actions
        cminteer @ KDonia-esristaff on May 1, 2019 3:39 PM
        Mark Correct
        Correct Answer
        Hi Kylie, no we have layers in the same file geodatabase which have fields with the same name which use the same domain (which of course is how domains work by design in a file geodatabase) which have been published to a single feature service in ArcGIS Online. After the feature service is in ArcGIS Online, the user (item owner, administrator) will change the domain list for one of the fields and then this error will occur. How can the issue be fixed in that case?
        Like • Show 0 Likes0
        Actions
        KDonia-esristaff @ cminteer on May 1, 2019 4:35 PM
        Mark Correct
        Correct Answer
        Ahh gotcha. This is a different way to hit the same error message (but is a different root issue), and unfortunately isn't one we've fixed yet. I've been able to repro what you are seeing. I'm guessing what happens is that ArcGIS Online has a single name for the domain, and leaves the name as-is when the one domain is edited. But now you have two different domains with the same name in the same hosted feature layer (which is what causes issues in Runtime, and so in Collector). If the changes to the domain are reverted, both layers load again. Let me follow up on this a bit and get back to you, but one thing that resolves it is if you were to publish the feature classes as separated hosted feature layers instead of as a single one.
        Like • Show 0 Likes0
        Actions
        cminteer @ KDonia-esristaff on May 2, 2019 6:50 AM
        Mark Correct
        Correct Answer
        Hi Kylie, that is correct.
        
        Publishing the feature classes as separate hosted feature layers is not a possibility in this case. This is a production service with data in it so implementing that "solution" would be very problematic.
        
        One thing that seems to "fix" it is to delete the domain list and re-create it. I would not want to do this manually for all of the affected domains though.
        
        I would be very grateful if you are able to follow up and find out what other solutions there may be. This is pretty major for us.
        Like • Show 0 Likes0
        Actions
        cminteer @ KDonia-esristaff on May 6, 2019 10:51 AM
        Mark Correct
        Correct Answer
        Hi Kylie,
        
        Can the scope of the changes to fix services in AGOL be expanded to include hosted feature services created from Pro? I can see no way to fix current production services without major changes to schema or deployment which would impact all client apps using the services (we have a JavaScript API Web app, and a cross-platform mobile app, both of which are in use at more than 20 customer locations). Currently it looks like this means we have to revert our mobile solution from Runtime 100.5 back to Runtime 100.1 (the last version of runtime that didn't have some bug that prevented us from using it, and which does not have this problem with the LoadAsync() choking on layers). That's obviously not a good long term solution. We want to be on the latest Esri Runtime for many reasons.
        
        Currently we've opened a support case about this aspect of the issue, Esri Case #02317535 - Not all layers get loaded (in Collector, or in Runtime app). That case is new and hasn't yet been worked or escalated.
        
        We are just looking for a workable solution at this point. Any help you can provide is appreciated.
        Like • Show 0 Likes0
        Actions
      - bmcelroy_hrc_engr @ KDonia-esristaff on May 14, 2019 5:31 AM
        Mark Correct
        Correct Answer
        Kylie, instead modifying the values by adding/removing a space or something similar, should reordering the values in the list also result in a new domain name?
        
        We were receiving this error and found through the JSON that we had two layers in a feature service with an identical field name and an identical domain name, but a different order of values. The domain existed in the original geodatabase the data was posted from so it must've been reordered through AGO.
        
        After reordering one list to match the other, the error stopped. However, the JSON still shows the same domain name.
        Like • Show 0 Likes0
        Actions
epescatore Mar 27, 2019 7:28 AM
Mark Correct
Correct Answer
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?
Like • Show 1 Like1
Actions
- aklimek @ epescatore on Mar 28, 2019 10:08 AM
  Mark Correct
  Correct Answer
  I am experiencing same issue. Worked fine in Collector yesterday (March 27); get Error 3054 today. Not experiencing the issue when using Classic.
  Like • Show 0 Likes0
  Actions
skiley Mar 28, 2019 10:13 AM
Mark Correct
Correct Answer
I worked with Esri support on this issue. The fix was to export the hosted feature layer having the problem to a file geodatabase and re-publish it back to the organization. It's probably also a good idea to make a new web.
Like • Show 0 Likes0
Actions
rblash Apr 17, 2019 7:40 AM
Mark Correct
Correct Answer
Kylie Donia can we have a full accounting of what can cause this error? I have a layer that was working fine until I added a domain value and updated the edit templates. Now I an seeing this error. These are basic processes that shouldn't be causing an error somewhere else.

Esri needs to be more transparent here. I (and I'm sure most others) do not have the time to spend an hour+ on the phone with tech support to ultimately be told to republish the data. The users need to understand what's going on.
Like • Show 0 Likes0
Actions
- KDonia-esristaff @ rblash on Apr 18, 2019 2:56 PM
  Mark Correct
  Correct Answer
  Hi Rob - Thanks for your patience on this. So far, we have identified a few causes of this error (one being the duplicate coded value domains that we've talked about here, and which ArcGIS Online has fixed for new data). We are still in the process of identifying and handling the various causes and find workarounds for them (without republishing) where possible.
  
  The other cause we've noticed has to do with editing coded value domains while the map is open in Collector (and in that case, restarting the app is the workaround, as reloading the map isn't enough). We are still in the process of understanding the conditions required to hit this issue. Are you doing your domain editing on a hosted feature layer? If so, does the map open if you restart the app?
  
  This is why I recommended
  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.
  We aren't sure all the cases yet and don't want to send people down the wrong path if in fact their case doesn't meet the requirements of one that we know. When working with support, we get the details and information to reproduce the error the same way you are, and can use that to understand if it is a different case and what is being encountered.
  
  Know that we are trying to understand the causes for this so that we can fix them, and thanks for helping us do so!
  2 people found this helpful
  Like • Show 0 Likes0
  Actions
  - rblash @ KDonia-esristaff on Apr 18, 2019 5:03 PM
    Mark Correct
    Correct Answer
    Thanks for the reply Kylie. Apologies if I came off rude in my post, however there is a bit of frustration on my end when hitting these sort of issues, particularly because I've had a handful of bugs impact my workflows between the latest AGOL and Suvey123 updates. With that said, I do understand how contacting support is integral to the process, but please understand that it is a time consuming effort. A single support request can eat up 3-4 hours of my time (time that's simply not in my project budgets) and they often do not result in a resolution to the problem. Also, as a consultant, I'm always working with client's data so sharing the data for support requests is quite often not possible.
    
    In regards to the specific issue I was posting about, I made a domain update to a hosted feature service layer via the item's settings page. Afterward, the layer failed to load. I had Collector open on my iPad when making the update, and (as you stated) re-opening the map didn't help. I can't recall if I shut down Collector anywhere along the way or simply re-loaded the map after each attempted fix (I tried a whole bunch of things), but in the end the layer did show up again after deleting the domain entirely then re-creating it.
    Like • Show 1 Like1
    Actions
Jostein.Svegardengeodata-no-esridist May 2, 2019 6:30 AM
Mark Correct
Correct Answer
I'm not sure if I understand the answers on all these different cases. For me, I have a web map that contains three editable layers (point, polygon and polyline fcs from the same database). All of them have a field TYPE that use the same coded value domain. All these three layers work fine in Collector, but I have a fourth layer (read only) from the same database that won't show. This layer does not use the same coded value domain or have a TYPE field. Then, my fifth layer (read only) from another database shows up just fine. All the featurelayers in the webmap is published on a standalone ArcGIS Server, and registered as items in Portal. There is a lot of talking about updates to ArcGIS Online in this thread, but what about Portal? What could be the cause to the problem I see? Everything works just fine in Collector Classic
Like • Show 1 Like1
Actions
- KDonia-esristaff @ Jostein.Svegardengeodata-no-esridist on May 6, 2019 11:32 AM
  Mark Correct
  Correct Answer
  Hi Jostein - Since your issue appears to be unrelated to the domains, could you please start a separate thread with your information? Thanks!
  Like • Show 0 Likes0
  Actions
bmcelroy_hrc_engr May 14, 2019 4:35 AM
Mark Correct
Correct Answer
We were also receiving this error on the new version of Collector while the web map worked fine in AGO and Collector Classic. Turns out we had two layers in the same feature service with an identical field name like described above, but our issue was the values in the domain lists were not in the same order. Once we reordered the values in one list to match the other, the error stopped.
Like • Show 0 Likes0
Actions

Incoming Links

Re: Map Download Failed with new 18.1.0 version

GeoNet

The Esri Community

Not all layers get loaded in Collector for ArcGIS

Outcomes

Related Content

Recommended Content

Incoming Links