Latest Contributions by MikeMillerGIS

Try Asset Package to Geodatabase, it creates a new geodatabase, stages the UN and then applies the asset package.  This will eliminate some variables. ... View more

What are your parameters?  What is your target GDB type?  Have you tried Asset Package to Geodatabase? ... View more

The Trace Results to GDB and Export Reporting Data could be used, but the output is neither an Asset Package or Utility Network.   ... View more

The  https://doc.arcgis.com/en/arcgis-solutions/latest/reference/other/ElectricExpanded_DataDictionary.ht...  replaces the link you provided.  That link is for the older version of the solution and we cannot change it due to version control ... View more

Attribute Rules are not supported in ArcGIS Online.  Forms support Arcade, but that profile does not allow the ability to insert rows into other classes. ... View more

Correct ... View more

You still should only change the name field when it is different.  So you should look at doing it this way: // Need the expects as we are accessing attributes via variable key, this tells the code to retrieve these fields Expects($feature, "NAME","NAME1","NAME2","NAME3"); var fglobalId = $feature.FEATUREGLOBALID; var name_fields = ["NAME","NAME1","NAME2","NAME3"]; var main_fc = FeatureSetByName($datastore, "Main_FC", ["GLOBALID", "NAME","NAME1","NAME2","NAME3"], false); var related_main_fc = Filter(main_fc, "GLOBALID = @fglobalId"); var updates = []; for (var f in related_main_fc) { var atts = {} for (var i in name_fields){ var name_field = name_fields[i]; if ($feature[name_field] == f[name_field]){ continue; } atts[name_field] = $feature[name_field]; } // IsEmpty does not work on dicts, so convert to text to see if empty if (text(atts) == '{}'){ continue; } Push(updates, { 'globalId': f.GLOBALID, 'attributes': { 'NAME': $feature.NAME } }); } if (Count(updates) == 0 ){ return; } return { 'edit': [{ 'className': 'Main_FC', 'updates': updates }] };   ... View more

We added a new switch state called Open-Traceable.  This switch state is a condition barrier for the subnetwork definition.  One Tie Switch would be set to Open, and one set to Open-Traceable.  When you run Export Subnetwork, you override the Subnetwork Definition and remove this condition barrier.  The de-energized section is included in the subnetwork that the Open Traceable tie switches subnetwork.  The phase information of that section is still reported as De-energized, as result of propagation is not recalculated on Export Subnetwork.   Some more info here - https://www.esri.com/arcgis-blog/products/utility-network/electric-gas/utility-network-design-to-operations  ... View more