Latest Contributions by MikeMillerGIS

You can just copy those classes as is.  No need to migrate them.   ... View more

Asset Group Unknown cannot be used in associations, rules, and other things.  It is really a parking lot for data until it has a known asset group.  You need to remove the associations to Unknown. ... View more

Could be, I never tried to work with a M:N in arcade. ... View more

Try this, my only guess is that adds or deletes is an empty array and maybe that is causing an issue // Arrays to store edits var edits = []; var adds = []; var deletes = []; // Get all District features var allDistricts = FeatureSetByName($datastore, "District"); // Find District features that intersect this Municipality feature var intersectingDistricts = Intersects(allDistricts, $feature); // Determine which District features that this Municipality overlaps with 80% or more var overlappingDistrictGlobalIds = []; for (var district in intersectingDistricts) { var districtGeometry = Geometry(district); var districtArea = Area(districtGeometry); var intersectionGeometry = Intersection(Geometry($feature), districtGeometry); var intersectionArea = Area(intersectionGeometry); if ((intersectionArea / districtArea) >= 0.8) { // This district overlaps, so store the GlobalID for it Push(overlappingDistrictGlobalIds, district.GlobalID); } } // Determine which relationships to add (new District features that overlaps with at least 80%) var relatedDistricts = FeatureSetByRelationshipName($feature, "Municipality_District_Rel", ["GlobalID"]); for (var index in overlappingDistrictGlobalIds) { var districtGlobalId = overlappingDistrictGlobalIds[index]; Console(districtGlobalId); var relatedDistrict = First(Filter(relatedDistricts, "GlobalID = @districtGlobalId")); if (relatedDistrict == null) { // A relationship didn't exist, so add it Push(adds, { 'attributes': { 'Municipality_GlobalID': $feature.GlobalID, 'District_GlobalID': districtGlobalId } }); } } // Get existing relationships between Municipality and District features var allRelationships = FeatureSetByName($datastore, "Municipality_District_Rel", ["*"]); var relationships = Filter(allRelationships, "Municipality_GlobalID = '" + $feature.GlobalID + "'"); // Determine which relationships to delete (no longer overlapping with at least 80%) for (var relationship in relationships) { if (!Includes(overlappingDistrictGlobalIds, relationship.District_GlobalID)) { // No longer overlapping enough, so delete the relationship Push(deletes, {'GlobalID': relationship.GlobalID}); } } // Return edits dictionary if there are changes to the relatio if (Count(adds) == 0 && Count(deletes) == 0) { return; } var edit_payload = { 'className': "Municipality_District_Rel", } if (Count(adds)){ edit_payload['adds'] = adds } if (Count(deletes)){ edit_payload['deletes'] = deletes } Push(edits, edit_payload); return { 'edit': edits }; ... View more

Take a look at the Create Association Record tool in the utility network package toolset https://doc.arcgis.com/en/arcgis-solutions/latest/tool-reference/utility-network-package/create-association-records.htm ... View more

I posted a pre-release of version of the UDMS for 3.5 that supports maintaining attachments in the Transfer UN Data tool - https://github.com/Esri/Utility-Data-Management-Support-Tools/issues/64 ... View more

The only other way is added a directional device so the blue controller cannot trace to the yellow controller. Something like a network protector right after the yellow controller. ... View more

You will need to open another device to isolate the yellow subnetwork from that section then.  In the current state, the network sees two subnetworks on that line.  Meaning it is energized from both directions.   ... View more

Then you need to define a condition barrier that separates those two subnetworks at that device.  You need a condition barrier for both NS is open or OS is open.  ... View more

Is the device between the blue and yellow a subnetwork controller?  Can you verify the blue line is connected to a different controller than the yellow line? ... View more

This is as expected in a version with eventing off.  This is caused by how Branch versioning works.  In a version, a row only exist if it was modify.  So take Eds example 1: Create Version - At this point, there are zero records with that branch ID 2: Open Fuse - This edit adds a new record to the device table with the updated attributes.  The Branch ID of that row references this active version 3: Save/Validate/Update Subnetwork- Since there is only one row with this versions branch ID, this is the only record that can be updated.  If Update Subnetwork were to update the affected down stream features, those edits would show up in default.     Hopefully this helps.  Running a subnetwork trace will display the correct results.   ... View more