Latest Contributions by Brian_McLeer

Trying to hyperlink to a website (var URL below) if the cabinet status is Active, I would like to return "available, please click here to sign up for service" with the "click here" acting as a hyperlink. The code works below without, but when trying to link it is just showing the full HREF code.    var intersectLayer = Intersects(FeatureSetByName($map, "HiLight Availability"), Buffer($feature, 0, 'feet')); var zones = ""; var URL = "https://www.website.com"; if (Count(intersectLayer) > 0) { for (var f in intersectLayer) { if (f.CabinetStatus == 'Active') { zones = 'available'; break; // Exit the loop if an 'Active' status is found. } else if (f.CabinetStatus == 'Future') { zones = 'anticipated for future development'; break; // Exit the loop if a 'Future' status is found. } else if (f.CabinetStatus == 'Planned') { zones = 'planned'; break; // Exit the loop if a 'Planned' status is found. } else if (f.CabinetStatus == 'In Progress') { zones = 'in progress'; break; // Exit the loop if an 'In Progress' status is found. } } } else { zones = 'not available at this address'; } return lower(zones);   ... View more

Functionality in model builder to click and pan around the model similar to as you would in a map in ArcGIS Pro would be beneficial rather than having to use the arrows to move around the model.  ... View more

When viewing content in AGOL or Portal, at the organization setting level choosing the default view of Table, List, or Grid would be a good enhancement. Currently, when you view content the default setting is the grid choicewhich is not ideal in every scenario.        ... View more

In preparation for migrating our water distribution system from geometric network (GN) to utility network (UN), we are adding all of the UN fitting types into our GN fitting domain. When creating several thousand new fitting types, I am unable to add fittings into the existing GN. I have tried both append and copy and paste. The error I am receiving is Warning 000594: Invalid Function Arguments. I have tried various steps from the solutions section below, but still getting errors. One other oddity is that there are about 33,000 new fittings to load, and about 11,000 did load successfully during the initial append.  My workspace is Enterprise 10.9.1 in ArcGIS Desktop 10.8.2 (has to be in ArcMap because of editing in a GN).  Description These specific input features require attention. This often occurs when features are positioned outside the current XY Domain environment. The XY Domain environment sets the allowable coordinate range for x,y coordinates. If a feature falls outside this range, it cannot be added to the output. In addition, with some tools such as Append, which have a target dataset, if the features of the input fall outside the XY Domain of the target, they also will not be added. Similarly, the M Domain and Z Domain limit the coordinate range for m- and z-coordinates. Solution Check the XY Domain, M Domain, and Z Domain environments, and reset them to Same as Input' if they are too restrictive for your inputs. When using a tool like Append, check the coordinate system of the target dataset, and if unknown, define a coordinate system for the feature class. Also, consider creating a new feature class with a broader x,y domain if the current x,y domain is too restrictive. ... View more

When you right-click on the Maps folder in Catalog and choose a new map, it creates the map and automatically gives it the name "Map". To rename, you have to right-click and choose rename. Adding the function to name the map upon initial creation would be an enhancement.  ... View more

In ArcMap, when you right-click in the Catalog pane you had the option to create a composite locator. While the option to add a locator is in Pro, the option to create a composite locator is not. You can still create a composite locator, but only by using the geoprocessing tool.   ArcGIS Pro:   ArcMap:   ... View more

When adding new Contingent Values to an existing Contingent Value list, being able to sort alphabetically on fields would help with organization.  ... View more

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