Latest Contributions by EdwardBlair

We are working with a mobile solution vendor that relies on ArcGIS sync-enabled feature services to replicate enterprise data to mobile devices.  The services all reference non-versioned, archive-enabled feature classes in an enterprise Geodatabase.  We're following the 'pre-planned' model where we create the initial 'golden' mobile geodatabases on the server and distribute these initially to all clients.  The first time a mobile user connects to the server it is supposed to be 'registered' with the enterprise - obtaining a new replica ID that will subsequently be used to determine what enterprise updates need to be propagated on later "synchronize" events. Many, maybe even most times the initial registration task will succeed.  Unfortunately, we've found that in a noticeable number of cases the registration does NOT succeed, meaning that subsequent synchronization will not occur.  This is bad. It seems that once registration has failed, further efforts at registration will also fail.  We haven't seen any pattern for registration attempts that fail versus attempts that succeed -- not to say there aren't any, we just have not seen them. The vendor says they cannot replicate the issue.  No comment warranted here. Comments from anyone has experienced this, or knows anything of this behavior, would be greatly appreciated. Thx, Ed ... View more

We step up replication from a versioned production Geodatabase into versioned replica about a month ago.  We haven't synchronized for several weeks.   There have been thousands of edits performed in the interval.  When we just recently performed a sync only a handful of features were copied to the replica.  Based on a CREATED_DATE field we can easily see that some classes were not moved at all. When we set up the replica we had a DBA make a new Oracle instance and load a backup from production, so on creating the replica we simply registered all the classes - and we made sure all classes were registered. So, the question is, what could make the sync send only a handful of features when we expected many? Any insights would be much appreciated. Thx, Ed ... View more

We are testing sync-enabled feature services to update mobile geodatabases on field user computers.  Data updates from the server seem to transfer fine.   We just tested changing symbology in the published feature service hoping this would be reflected on the mobile clients on replica syncing, but this does not seem to be happening.   What should our expectation be here?  Is a symbology change in this case equivalent to a schema change and we need to re-create each of the replica mobile geodatabases? Any insights would be much appreciated. Thx, Ed ... View more

We're experimenting with use of sync-enabled feature services to support a mobile application.  We're using archiving as opposed to versioning to detect changes.  In a simple test I added a new feature to the parent feature class in the enterprise geodatabase to see if it would sync down to the client (a runtime geodatabase on a laptop).  Eventually the new feature showed up on the client -- which is good.   However, I noticed that ALL of the features in the runtime gdb had the same gdb_from_date value as my new feature.  I would have expected my new feature to have a layer gdb_from_date than all other records.   Which prompts my question, what/how much information is actually transferred to the client on a "sync"?   I thought it would be only the changes since the last "create replica" or "sync replica" operation.   But it seems like it might be re-sending the entire dataset. Any insights would be much appreciated. ... View more

In ArcObjects there is the IZAware interface we can use to make an existing 2D geometry aware of Z-values.   I can't find the equivalent in the ArcGIS Pro SDK -- but there must be a way to do this.  How can I, for example, change a polyline that may include a parametric curve from a 2D polyline to a 3D polyline? ... View more