Latest Contributions by Brian_McLeer

After recently adding a Network Analyst Route Layer to Portal, the directions widget is showing driving miles and estimated time of arrival, but not total driving minutes. Any ideas on why? It should be showing a total number of minutes of driving time if it can calculate the estimated time of arrival.    ... View more

In using the workflow from this article from @HusseinNasser2 , when moving a point feature associated with a polygon, I receive the error in the image below. Does anyone have any insight? My environment is a SQL Database on Enterprise 10.8.1 and ArcGIS Pro 2.6.7. Also, we are upgrading I have tested on an Enterprise 10.9.1 and ArcGIS Pro 2.9.1 environment as well yielding the same results.      Attribute Rule Expression:       //The attribute rule is added to the pointClass on the Field field on update //buffer the point feature 40 feet, this will give us a circle polygon geometry var bufferedGeometry = buffer($feature,0) //get the guid of the point feature being updated var AssetID = $feature.AssetID //find the buffered geometry feature var fs = FeatureSetbyName($datastore, "Database.Owner.ParkStructurePolygon") //by filtering on the pointGuid var bf = filter(fs, "AssetID = @AssetID") //if we couldn't find it exit (someone might've deleted it) if (count(bf) == 0) return $feature.AssetID; //get the feature row (we should only have one ) var bufferedFeature = first(bf) return { //we want to just return the value of field `Field` no change require "result": $feature.AssetID, //this keyword indicates an edit that need to happen, its an array since we can make many edits "edit": [ { //the other class we want to edit "className" : "Database.Owner.ParkStructurePolygon", //the type of edit, in this case we want to update so we say `updates`, its an array since we can make many updates "updates" : [ { //what feature we need to update? we can either find it by the globalid or the objectId "globalID" : bufferedFeature.globalID, //what do we want to update (we can optionally add attributes property and update properties there) "geometry": bufferedGeometry, "AssetID": $feature.AssetID, "Comments": $feature.Comments, "Description": $feature.Description } ] } ] }         ... View more

We are starting to migrate our enterprise database from traditional to branch versioning. The recommended SDE admin workflow (link below) for traditional versioning is to delete \ create versions after editing is complete on a version. At our organization, we reconcile\post, delete versions, compress, rebuild indexes, analyze, create versions via nightly Python routines. With migrating to branch versioning, compress is no longer needed, and you cannot rebuild indexes (indices?) on branch versioned data.  My question for the community is it still necessary to delete\create branch versions on a daily schedule after an editor has completed edits for the day? Or is this becoming obsolete, such as compressing the database is as ESRI recommends migrating to branch versioning.    https://desktop.arcgis.com/en/arcmap/10.3/manage-data/geodatabases/recommended-version-administration-workflow.htm ... View more

When publishing branch versioned data for the first time changing from traditional versioning, allow for required fields to be turned on by the right-click option in the 'Share As Web Layer' pane. I received 465 errors which I have to go into each layer and turn on all fields that are required to be turned on to publish branch versioned data to Portal. Being able to select the errors, right-click and choose 'turn on field' would be a great improvement.    ... View more