Latest Contributions by JoeHershman

We have a situation where at times to working areas may be pretty close together, and when the occurs the offline area overlaps.  At times there may be a significant amount of data collected in one of these overlapping areas So what is happening when a user wants to takes area 2 offline, they will also pull all of the data collected as part of area 1.  And when syncing between these two offline maps they are still including the other area. What would be nice is if we could define a where clause as part of taking the map offline, so we only pull data associated to a specific project number.   Is this possible? Associated to this is that we were hoping to allow crews to collect existing data near the work areas (because this data is collected with GPS it is a chance to improve accuracy), so for this reason we give a good size buffer around our boundary when taking the project offline. Thanks -Joe ... View more

I am trying to creating a relationship in data that is created from taking a map offline and it does not seem to have any effect.  The code takes a list of vertices for a line and creates features that should then relate back to the line foreach (var vertexInfo in Vertices) { var vertexFeature = (ArcGISFeature) vertexTable.CreateFeature(); vertexFeature.Geometry = vertexInfo.MapPoint; if ( vertexInfo.NmeaLocation != null ) { UpdateGpsAttributes(vertexFeature, vertexInfo.NmeaLocation); } await vertexTable.AddFeatureAsync(vertexFeature); Log.Debug($"Relate Feature Origin: {feature.FeatureTable.TableName}:{feature.GetAttributeValue("OBJECTID")}"); feature.RelateFeature(vertexFeature); Log.Debug($"Relate Feature Destination: {vertexFeature.FeatureTable.TableName}:{vertexFeature.GetAttributeValue("OBJECTID")}"); }‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍ Everything runs without error and the features are created, however, the RelateFeatures does not do anything.  If I look at the services the relationships are defined: In Vertex Feature Service: "relationships" : [ { "id" : 0, "name" : "PipelineLine", "relatedTableId" : 3, "cardinality" : "esriRelCardinalityOneToMany", "role" : "esriRelRoleDestination", "keyField" : "PipeLineGlobalID", "composite" : true } ], ‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍   In PipeLine Feature Service: "relationships" : [ { "id" : 0, "name" : "Vertices", "relatedTableId" : 17, "cardinality" : "esriRelCardinalityOneToMany", "role" : "esriRelRoleOrigin", "keyField" : "GlobalID", "composite" : true } ], ‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍ This is a look Vertex at the table in the offline database, as you can see the PipeLineGlobalID relationship field is left null: The log shows that the code to do the relate is running The relationships are created in ArcGIS Pro prior to publishing the services to AGOL. Any reason why this relationship does not get created? Thanks -Joe ... View more

When one switches the Utility Network Display Content you get these annoying notifications that there is no filter on certain layers.  Well of course there are no filters because the layers do not have associations.  Can this be turned off someway? Thanks -Joe ... View more

I am trying to change the default version of our branch versioning to be protected instead of public to keep peoples from inadvertently editing directly in default. It would seem that this needs to be done with the Alter Version (Data Management) tool.  However, I cannot get this to run successfully.  I have tried to do this both using the feature service connection and to use the direct database connection. Doing the feature service connection I get an error that seems to possibly be something with permissions, but I am connected to Enterprise as the owner of the feature service    Running using the direct connection the user seems to be associated to the name I am using for the version, but I have tried a lot of different combinations, from documentation I would think it is  serverfolder/servicename.sde.default.  As mentioned, though, I have tried lots of different combinations some with https others without. Any thoughts on why this will not work and how I could make this change.  I am thinking just change in the underlying versions table in sql server, but concerned that might be a side affect to this Thanks -Joe ... View more