Latest Contributions by ColinLawrence

Hello Bill, I hope I can help you out. What version of Collector are you using? When you load a map or tap + to add a new feature, it should pan to your current location. Are you saying your current location (blue dot) is appearing in California when you are in South Carolina? When you mention looking at different basemaps, are you using different maps or switching the basemap from the basemap tool within Collector? Regards, Colin ... View more

Hi Thomas, The "Device will use a tile package it already has" setting is not a Collector setting. It is found in the Offline - Advanced Options in the Web Map details. This is where you manage Offline Areas, sync, and basemap download settings. Instructions for this workflow can be found on our doc page. If you still have issues with this workflow please let me know.  Regards, Colin ... View more

Pam, Would you be able to share your map with us if in AGOL? If so, share the map and feature service to a group and invite the user Collector4Arcgis.  In the log file I see a familiar error, but would like to investigate the data setup if possible. "The field already exists." Thanks! ... View more

Hi Pam, Is this a pre-planned map area generated in AGOL? Are you able to add an On Demand area directly within the app? Colin ... View more

Hi Randy, Older versions of the Apps (including Explorer) have older versions of Runtime that do not utilize advanced symbology. These display simple symbology by default which is why the issue would not be reproduced.  Colin ... View more

Hello everyone, From initial investigations there seems to be an issue with the publishing process. The best method is to go through Support so we can gather more information about the cause. It does seem to be specific to Character Marker Symbols set in ArcMap before publishing. As Pro handles this symbology differently, a workaround is to publish the same data from Pro or, as noted, change the symbology within the Web Map in ArcGIS Online. Support should be able to get you attached to a relevant bug for further updates on the issue. Thank you for all of the feedback.  Regards, Colin ... View more

Claire, Did you try these steps from above? From the Windows start menu, select Settings > Apps & Features > find and select Collector for ArcGIS > Advanced options > check the storage size for the App. It should be about 59 MB. If you see a value that is significantly smaller, there may have been a problem with the installation. Typically this is caused by specific Windows Group Policy settings or anti virus program so it is best to work with your IT to narrow it down further. I have seen this effected by Microsoft Update Group Policy settings if that helps.  When it comes to installing outside of the store it is tough for us to troubleshoot as this can introduce many environment specific variables. It is best to work with your IT in this situation if possible. To potentially narrow the cause I might try installing on another machine to check for the same behavior.  Regards, Colin ... View more

Claire, Are you referring to the crashing behavior on Windows or iOS? The iOS crashing with Diego was caused by Group ordering in ArcGIS Online. Are you using a Group to share Maps and Data for Collector? Colin ... View more

Veronica, We are very happy to hear that this has enhanced your field workflows. Please don't hesitate to throw some more great ideas at us (via Geonet, Support, conferences or feedback within the app). Colin ... View more

Thomas, I am glad you were able to narrow it down. Would you be able to submit this to Support so a bug can be logged? This would be the most efficient way to close the loop on this issue and thread. Thank you! Regards, Colin ... View more

Thomas, I dont see any indication this was ever resolved with Support. As I mentioned before I believe this has to do with editor tracking fields. Can you check the schema of your problematic service? If you have editor tracking on you should only have these 4 fields: Editor Creator EditDate CreationDate The names could vary depending on how you added editor tracking, but there should not be any duplicates (ie. Editor_1). Let me know if you see something like this. Regards, Colin ... View more

Would either of you be able to send me some sample data that you are using to reproduce this issue? Send me a direct message and we can discuss further steps for sharing. Thanks! Colin ... View more

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