|
POST
|
Hi Recep, You can use iTunes and copy the Collector folder to your desktop or use the Files app in iOS to share your user folder (under Collector folder) to email/one drive. The runtime geodatabase contained within the folder is consumable in ArcGIS Pro; you can export the data or attempt to sync from Pro. When did you start having this sync issue in Collector? Regards, Colin
... View more
08-03-2020
04:55 PM
|
1
|
0
|
712
|
|
POST
|
We are actively investigating this issue but are finding it difficult to reproduce. I encourage those who are experiencing this issue to reach out to Technical Support and explain what you are experiencing. If details surrounding the workflow and the data being used can be provided that would be extremely helpful in continuing to troubleshoot this. There is an existing BUG that you can be attached to. Regards, Colin
... View more
08-03-2020
04:09 PM
|
1
|
1
|
3565
|
|
POST
|
Did some quick research on the bug number and it actually falls under Online and not Pro, so it would be (hopefully) addressed in the next quarterly ArcGIS Online release (sept/oct typically). Regards, Colin
... View more
07-10-2020
03:35 PM
|
2
|
0
|
3326
|
|
POST
|
Steve, The appropriate route is usually going to be going through Support simply for the reason that someone is accountable for looking into your issue. While I and others try our best to monitor Geonet and other outlets, things do tend to slip through the cracks sometimes. I do work on our Field apps team but am knowledgeable in other areas and could see if I have some input. The layer you reference that you are turning on tracking for, is this a new layer created in AGOL or something recently published from Desktop? If coming from desktop, did it have editor tracking or the editor tracking fields already added before publishing? Also, where are you viewing this information that shows incorrectly - in a popup in the map, the attribute table, or the item details (data tab) for the Feature Layer? These are all good places to double check. Regards, Colin
... View more
07-09-2020
06:07 PM
|
2
|
5
|
3326
|
|
POST
|
FYI there is a bug logged (BUG-000131801) for this through Tech Support. I encourage you to contact them and get yourself attached so we can effectively gauge how many are impacted by this. Colin
... View more
07-01-2020
05:04 PM
|
0
|
1
|
2857
|
|
POST
|
This is something that got my thinking for sure. I will bring this up to some other relevant teams to see what could be done but as you say, the solution is not so easy. You could also log this as an Idea on the ideas site here. For your other scenario, as a general rule, last edit in win so I imagine that is what would happen. I hope this info helps a bit! Regards, Colin
... View more
06-25-2020
06:05 PM
|
0
|
2
|
2473
|
|
POST
|
Hi Travis, I think this is a really good question and unfortunately I dont have a definitive answer for you at this point, but I thought I would chime in. What you have identified is likely expected behavior. I believe the relationship between View Layer and its Parent are handled at the feature service level (online). When you take a make offline the data is packaged into multiple sqlite databases. These databases are likely not aware of the relationship between the two layers and therefore and updates to each other would only be recognized after a sync is performed. Have you tried using sync in the map after making the changes you explained? Regards, Colin
... View more
06-25-2020
05:32 PM
|
0
|
4
|
2473
|
|
POST
|
Erica, Sorry I lost track of this one...are you still having issues with your View layer? It may warrant opening a case with Tech Support if you have not already. Regards, Colin
... View more
06-25-2020
05:24 PM
|
0
|
1
|
2473
|
|
POST
|
Craig, This isnt currently possible in Collector. You may have seen the announcement for Field Maps. Within the first release later this year there will be included some smart form capabilities; this should include conditional logic such as the situation you describe. Currently, you can accomplish a similar workflow in Survey123. Regards, Colin
... View more
06-24-2020
09:15 AM
|
0
|
0
|
2080
|
|
POST
|
HI Erika, I understand your concern about uninstalling; its something that we can do easily in testing that is less viable in some real world scenarios. I finally had the opportunity to test this a bit further to jog my memory and potentially found whats going on. Do you happen to be placing the .vtpk directly into the Basemaps folder using the Files app? Packages should be placed in the root Collector folder, as Collector has logic to distribute these in the proper location (indv folder under Basemaps) when the app is launched. For example: I had a fresh install of Collector (no basemaps folder) and sideloaded a vtpk via OneDrive to the Collector folder. After closing and re-opening Collector I see the .vtpk as expected. Inspecting the Collector folder there is now the Basemaps folder and 1 folder under that, representing the .vtpk. I tried the process again with another vtpk, placing it in the Basemaps folder -- Collector did not recognize this one. I used the Files app to move the problematic vtpk from the Basemaps folder up to the Collector folder, closed and relaunched Collector, and found that Collector now recognized the .vtpk. Looking back in the Files app the .vtpk had been placed in its own folder under Basemaps as I would expect. Note: When using itunes to sideload a basemap it doesnt even let you access the basemap folder. This is the reason for the logic mentioned above. It seems odd that you are only having issues with one vtpk in particular so I am not sure if this is the cause, but have you tried moving this problematic .vtpk to the root Collector folder and relaunching? Regards, Colin
... View more
05-28-2020
05:50 PM
|
0
|
6
|
2711
|
|
POST
|
Hi Aaron, If you cannot use the editor tracking "defaults" you could try to edit your existing fields to mimic what is expected. I cannot say for certain this will work as I haven't had a chance to test this workflow myself. However, if you are comfortable doing this I would say its a worthwhile alternative while you wait for a resolution on our end. Regards, Colin
... View more
05-28-2020
09:50 AM
|
2
|
0
|
1752
|
|
POST
|
Hi Aaron, A bug was logged with Support and we are currently investigating the best way to handle this issue. If you would like to be attached to the bug for tracking purposes, please reach out to support and request to be added to BUG-000129003. These problems can arise based on different ways editor tracking fields can be configured. Some may want to configure editor tracking fields in their own ways or using their own pre-configured fields. This can lead to problems and we are trying to sort the best way to handle these problems; whether thats a more helpful error or adjusting to consume them as is. Some examples of potential issues we have seen include: adding default values to editor tracking fields, setting editor tracking fields to be non-nullable, or setting the editable property to be true. These all seem like good ideas on paper but are not how editor tracking fields are designed to be handled. I hope this helps. Regards, Colin
... View more
05-27-2020
04:51 PM
|
1
|
1
|
1752
|
|
POST
|
I think the key here is the process of transferring from the computer to the device. In the case you are having issues with, this was done via OneDrive. During this process we had also experienced an issue on our end. Unclear if this was network related or OneDrive related but it didnt seem reproducible at the time. Moving around packages via the Files app shouldnt be the problem as this was tested more extensively. We envisioned the scenarios where an administrator may use Airdrop to distribute packages from their device to fieldworker's devices thereby sidestepping the process of connecting each device. You can then use Files to place the package in the Collector folder and Collector should handle it from there. You still need to load it to the first device by which the recommended method is Itunes. If you want to go a bit further it could be a good idea to reinstall the app, thereby cleaning out the Basemaps folder altogether and eliminating that as the potential cause. Regards, Colin
... View more
05-20-2020
02:16 PM
|
1
|
8
|
3940
|
|
POST
|
During development we saw what seemed like a one off issue of a corrupt package when transferring via OneDrive. I am not sure if that is the case here but it does make me suspicious. I would recommend using iTunes/Files app if at all possible to sideload basemaps. Once a basemap is placed at the root Collector folder, it will create the basemap folder (if necessary) and distribute the package to the correct subfolder(s). Perhaps you also had an issue with the existing Basemap folder in your first test as well? Regards, Colin
... View more
05-20-2020
11:55 AM
|
0
|
10
|
3940
|
|
POST
|
Hi Matt, It looks like you are using Collector Classic. For clarification, you updated your iOS from version 9.x to 11.x? Perhaps something changed in the way iOS organizes the folders between these versions. If you are able to do so, connect your device to your computer and go to your device in iTunes. Browse to the files shared with the device and select the Collector app. There should be a 'basemaps' folder if you have basemaps stored on the device recognized by Collector. If not, you may need to transfer again. I believe the Files app was introduced at iOS 11 which allows you to accomplish the same workflow above directly on your device Regards, Colin
... View more
05-06-2020
05:19 PM
|
0
|
0
|
1395
|
| Title | Kudos | Posted |
|---|---|---|
| 1 | 3 weeks ago | |
| 4 | 3 weeks ago | |
| 1 | 04-14-2026 09:11 AM | |
| 1 | 03-18-2026 11:54 AM | |
| 1 | 03-06-2026 02:09 PM |
| Online Status |
Offline
|
| Date Last Visited |
yesterday
|