Failed to Create Replica in Collector
So there was no dropdown in the Sync Model for "Per Replica" - there was only perLayer. Not sure of the order of xy on the extent but did both mins 1st, then maxes. Had to lookup the coordinate system for UTM NAD Zone 11 which I came up with as 2153. The basemap is a Tile Package in the same coordinate system.
I ran the request and received the following errors in the Manager log. The service is published with a GlobalID so not sure what the problem is.
Hi Karen,
I'll try to clarify a couple of things to see if we can help sort this out.
Firstly - the server log is indicating that there is not a GlobalID field on the "Facility_UtilHydrants_Pt". I'm assuming this is the table that is referenced by Layer 0 in your service?
Can you confirm in the back end geodatabase that this table has a field of Type "GlobalID" (not GUID).
Secondly...some clarification with the REST inputs.
The perReplica sync model is applicable for Versioned data.
The perLayer sync model is applicable for Non-versioned archived data.
So it makes sense that only the "perLayer" model is available to you based on how you prepared your data.
The format for the geometry looks something like this:
"xmin": -117.1756306304369,
"ymin": 32.70997289655956,
"xmax": -117.1568780005883,
"ymax": 32.73084570678091
I've included an easy way to make sure you are getting the formatting below.
The input and output SR parameters will default to the SR of the input data which is defined in the Service. So if you want to be consistent with this, then you do not need to supply Input Spatial Reference or Replica Spatial Reference. You can leave them blank.
Steps for easy way to get the proper formatting for the Geometry
1) Go to your Feature Service endpoint (i.e http://<yourServer>:6080/arcgis/rest/services/<yourFeatService>/FeatureServer
2) Click the JSON button at the top of the page... this will add "?f=pjson" to the end of the URL.
3) look for one of the extent items (i.e shown below) - and copy xmin - ymax portion
"initialExtent": {
"xmin": -117.1756306304369,
"ymin": 32.70997289655956,
"xmax": -117.1568780005883,
"ymax": 32.73084570678091,
"spatialReference": {
"wkid": 4326,
"latestWkid": 4326
}
4) Fill in your own extents
5) Copy paste this to your Geometry value
Here's an example of inputs to a service I have
Table has GlobalID - there is only one feature class in the service. Data is in UTM NAD83, zone 11 as per my previous post, so I put in parameters for that. Still same error. I can edit in connected mode - just not disconnected. It's a non-versioned Feature class with Archiving on as per specs. Wish that were not the case but oh well.
Hmmmm
Does the layer have attachments or participate in relationships? Attachments and RC need to be based on GlobalID fields. They cannot be based on the ObjectIDs.
http://resources.arcgis.com/en/help/main/10.2/index.html#//0154000006m1000000
If you do have attachments or Rcs, can you check the properties. You will want to Properties to specify that the GlobalID is the primary key field
If they are based on OBJECTID you can use the Migrate Relationship Class GP tool to migrate these from ObjectID to GlobalID.
http://resources.arcgis.com/en/help/main/10.2/index.html#//001700000193000000
You will need to republish the FS after this schema change .
