Latest Contributions by ColinLawrence

As an aside, in case it is important, I am using a sideloaded basemap for the map in question. I was hoping that taking the basemap out of the downloading equation would help to speed things up. In looking at the log file in Collector, it looks like that the offline area that did successfully download still downloaded the basemap used in AGOL, rather than honoring the advanced setting of "Device will use a tile package it already has." This might be a separate issue, but throwing it in here as well. I also might be misreading the log. The issue makes more sense after reading this bit. Referencing a sideloaded basemap using the advanced settings is not yet supported in the current version of Collector and will be introduced in the near future in a Beta and in the next release (19.1). That being said you should still be able to download the preplanned area which will include the Web Maps current basemap. So in regards to Sean's response, which basemap are you using in the Web Map? The log file shouldnt contain sensitive information, but you can send it to me in a message as an alternative. Colin ... View more

Livia, Have you checked back in AGOL in the Manage Areas screen; does it still say Generating there as well for your area? There was a known issue on the AGOL side, which shouldnt occur anymore, where areas would take an extended time to generate or get stuck in this process. If you are seeing that the area is generating in Collector but not in AGOL there is potentially some other problem and yes please create a new thread. You can attach your log there for reference. I hope this helps! Colin ... View more

Hi Livia, Because all of your data is coming from one Geodatabase, you would not run into this problem. From a Desktop perspective, the only situation you would see this is where you have two GDBs that both have a domain with the same name and you publish a collection of layers as a single Feature Service that have sources in each GDB with the 'duplicate' domain. As you are getting successful downloads using smaller areas I would say confidently this is not related. You can use the steps earlier in the thread to capture a log using the new version of Collector when the download fails; perhaps this will give us a hint.  Colin ... View more

Hello, I know this thread is over a year old but I wanted to comment to see if anyone is still having issues. We absolutely support the use Subtypes and Domains in Collector and have for some time; there have been known issues in the past. If someone is still having issues please comment with the platform and version you are having an issue with and I can take a look. Thanks! Colin ... View more

Good to know you got it working. I checked the status page for that day and did not see any interruptions, but it certainly does sound like some type of network issue. I you have not already, you may want to consider creating Offline Areas in ArcGIS Online ahead of time so the basemap and data are prepackaged; this cuts down greatly on download times.  Colin ... View more

Hi Aaron, Jay,  Which version of Collector are you using and on which platform? Did any of the downloads eventually fail? Colin ... View more

It does sounds like you are running into an issue with copied layers. The fact that copy layers works in Classic is coincidental and was not intended functionality. We hope to improve the documentation of this in the future.  In your situation I would suggest looking into Feature Layer Views or removing the copied layers from maps you intend to go offline with. I hope this helps! Colin ... View more

Katherine, The message you are seeing is more of a result and not an error message. You will see several of these come back in the logs when a download fails, but you will want to scroll a little further until you find the error message.If you are having trouble locating it, sometimes its easy to clear the logs first so you are not seeing older messages. Use the trash icon in the top right on the logs page and then reproduce the download failure again. Again you might have to scroll through some of the exploded map file messages, but your error should be in there.  Colin ... View more

Patrick, Glad you were able to get the original error sorted; I am not sure why the Web Map was thinking the layer was added twice.  In regards to the new error you are seeing, I have not seen that myself before. I dug around at it looks like this may be a quite misleading error message and may have to do with editor tracking fields and not duplicate fields or domains. I would get in contact with Support to further investigate this and if that turns out to be the cause they could attach you to a defect and help with any potential workarounds.  Colin ... View more

Do you have the same feature service added to the map twice? Looking in particular at this section of the error message: Unable to support duplicate feature layers: https://services3.arcgis.com/HK1JCkzRlbeqkjjf/arcgis/rest/services/AVG_Harvest_Trails_2018/FeatureServer/0already exists, NSLocalizedDescription=Illegal state, Additional Message=Unable to support duplicate feature layers: https://services3.arcgis.com/HK1JCkzRlbeqkjjf/arcgis/rest/services/AVG_Harvest_Trails_2018/FeatureServer/0already exists The same principles apply as would with copied layers; packaging into a runtime geodatabase (going offline) leads to undesirable behavior. If its necessary to display the same data multiple times in different ways, Feature Layer Views are the recommended practice.  Colin ... View more

Patrick, Your error message is a bit different. Do you happen to use copies of feature layers? See this thread if so. I wouldnt worry too much about that other thread regarding domains unless you are hitting that specific error. It was a defect with AGOL that has been addressed. The only situation to be careful of is bringing in data from multiple geodatabases which each have a domain with the same name, and publishing as a single service. There is no problem with using the same domain on multiple layers/fields in the same GDB.  Colin ... View more

Peter, I wouldnt say i'm recommending that practice; I was more assuming that this is what you used because its easier to run into this issue that way. Creating domains (and curating your data in general) will always be more powerful in Desktop. I would say the online interface is most useful for applying domains to layers created from templates in AGOL or quickly adding a new value to an domain. In regards to this error, things get a little more murky when your data is coming from Desktop, or at least harder to explain. If i'm remembering correctly, the two source layers would come from separate geodatabases and contain a domain with the same name (different geodatabase, different domain, same name). In this scenario all of the layers were published to the same service, but I see you have a service for each layer. It may be worth trying to republish this data (both harvest layers) as a single service as it sounds like they are indeed coming from the same geodatabase so you shouldn't have the issue noted above. Again your situation is less clear to me so I cannot say with certainty this will work. If it doesn't I would suggest logging a ticket with Support so it can be dug into further.  Colin ... View more

You can either post it here or send it to me in a direct message. These are also useful to provide to Support when you log a case with them, which depending on if its a known issue, I may have you do.  Colin ... View more

Katherine, Here is a screenshot, ensure you are tapping on your login name 3 times rapidly. There should be no dependencies on user type or login.  ... View more