POST
|
I'm running into a problem with the latest iOS Collector app. Keep in mind this pertains only to maps I've just created and downloaded to the device, not older maps that I've created and downloaded. When trying to view or create records in a related table with a downloaded map, the application crashes. No error, no nothing - the instance blinks out of existence. I've checked the same map on Android and no such problems. I'm able to view and add records to a related table without a problem. Anyone else have this problem? Thanks, Jason
... View more
09-01-2016
01:32 PM
|
0
|
0
|
415
|
POST
|
Hello, We were having problems syncing data from our iPads to AGO a while back. To back up this data, we copied the .geodatabase file and all associated data from the iPad to our local server. It was my understanding that I would be able to bring the data back in to a FGDB using the 'Copy Runtime Geodatabase to File Geodatabase' tool, but it seems not to be the case. I receive 'Error 001730' when I try to run this tool. Using ArcGIS 10.3, Collector 10.3, and AGO. Is there some setting I need to enable in order for this tool to work? Thanks, Jason
... View more
06-12-2015
03:00 PM
|
0
|
11
|
6743
|
POST
|
Hi Scott - thanks for letting me know I need to submit a support ticket. Could you let me know how to do that? I'm a bit new here in the forum. Thanks!
... View more
06-09-2015
01:09 PM
|
0
|
1
|
448
|
POST
|
I've found a workaround for this until the bug is fixed. For my map, I'm using a collection database and a background database. If I add a bunch of 'dummy' feature classes to the background database and publish the service with those dummy feature classes at the top of the TOC, those dummy feature classes are assigned the first numbers in the feature service. If you have enough of the dummy feature classes such that the first background layer you want has a number higher than those in the collection database, you can remove the dummy datasets from your map, leaving a unique number for each of your layers within the map. Relates work then. Any thoughts from Esri on fixing this bug?
... View more
06-04-2015
10:36 AM
|
0
|
3
|
448
|
POST
|
I forgot to send along the dataset. See attached. I also tried to download the map again and got a different error about parameters missing. Then I just tried it again and it downloaded without error, so I have no idea what's going on.
... View more
05-26-2015
02:25 PM
|
0
|
0
|
312
|
POST
|
Hi, I have a database with feature classes related to each (e.g. point feature class with a 1-M relate to a line feature class) and I've been able to publish maps with this up until last night. Has there been a modification to the publishing service? I now get the error "The map 'XXX' failed to download with the message: Unable to create replica. Please check your parameters., Error in creating runtime database." I ran some tests on a new, simple database and found I could publish with just a point and a related table, but once I add a related feature class, the error occurs. Using Collector 10.3 for Android and AGO. Thanks!
... View more
05-26-2015
09:13 AM
|
0
|
4
|
2774
|
POST
|
I've come upon what I believe is a bug in the 10.3 iOS Collector App. Background on my project - I'm setting up a field application where I have a GDB with related feature classes and tables that will be collected in the field, and I have another GDB full of background 'static' data (project boundary, roads, NHD, etc.) If I publish both databases to AGO as one feature layer and service definition, everything is A-OK. I then decided that I want my 'static' data as its own feature layer and service definition so I can change the project boundary or if another layer is desired, I don't have to redo the entire map. Here's where the problem begins: Looking at my map on the web, the relates are fine, as well as if I look at the map through an Android OS. When I look at and try to add data through the iOS app, the relates are pointing to the wrong feature class or table. I believe I know why: Looking at the URLs for my feature layers, I think that iOS is only looking at the array number and not at the feature layer part of the URL. For example, if I have two feature layers with two features in my map: <URL>/FeatureLayer1/FeatureServer/0 <URL>/FeatureLayer1/FeatureServer/1 <URL>/FeatureLayer2/FeatureServer/0 <URL>/FeatureLayer2/FeatureServer/1 If FeatureLayer1/0 is related to FeatureLayer1/1, iOS will show FeatureLayer1/0 being related to FeatureLayer2/1. This is not the case in the Android OS or through the web map. Anyone else run into this problem? It really messes up the efficiency you should have from using multiple feature layers in a map.
... View more
05-13-2015
04:05 PM
|
0
|
5
|
4159
|
Online Status |
Offline
|
Date Last Visited |
11-11-2020
02:24 AM
|