Latest Contributions by MikeMillerGIS

I would try this Start a brand new ArcGIS Pro sessions Do not add any maps Run the Asset Package to Geodatabase

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

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

-2 is invalid, a rule cannot be created for this combo. Some more info https://github.com/Esri/Utility-Data-Management-Support-Tools/blob/gh-pages/help/ImportExport_matrix.md

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

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

The most current docs linked on the solution site are below: https://doc.arcgis.com/en/arcgis-solutions/latest/reference/other/ElectricUnbalancedDistributionEssentials_DataDictionary.html https://doc.arcgis.com/en/arcgis-solutions/latest/reference/other/ElectricExpanded_DataDictionary.html

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.

Correct

The rules show that a 3 phase primary can only connect to line side, since there is not an ambiguous rule, an explicit terminal connection is not required, as the rules define that is can only connect to the one line and not the other.

That makes sense. The shipped version of the UDMS toolset was build for 3.1. A lot has changed since then and requires the new toolset. In upcoming versions of the foundations, we are removing the toolset and providing instructions on getting the appropriate version of the toolset from github. Writing tools that work in multiple versions of ArcGIS Pro with multiple different python versions has it's challenges and the best solution is to have a toolset per version of ArcGIS Pro.

Can these sheets be manually added and populated with stormwater related information (assuming we can figure out that information)? Or do we move along with the current SW DataMapping.xls table with the existing worksheets? - Unless you need them, should not affect anything - You can run the Create Simple Data Mapping and include the old sheet to carry it forward into the new schema - We ran the Create Migration Workspace GP tool in the SW Pro project, which failed. - What was the failure? The most recent version of the tools are here - https://github.com/Esri/Utility-Data-Management-Support-Tools

You need to specify a Domain Name, the validation should have caught this, but it looks like it is missing. Once you specify a domain name, you need to set the correct targetclass.

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 }] };

You need to check if each row has the same name. Try this: var fglobalId = $feature.FEATUREGLOBALID; var main_fc = FeatureSetByName($datastore, "Main_FC", ["GLOBALID", "NAME"], false); var related_main_fc = Filter(main_fc, "GLOBALID = @fglobalId"); var updates = []; for (var f in related_main_fc) { if ($feature.NAME == f.NAME){ continue; } Push(updates, { 'globalId': f.GLOBALID, 'attributes': { 'NAME': $feature.NAME } }); } if (Count(updates) == 0 ){ return } return { 'edit': [{ 'className': 'Main_FC', 'updates': updates }] }; * Edited code, no reason to return Geometry and also needed to add NAME to the FeatureSetByName constructor

Online Status	Offline
Date Last Visited	yesterday

My Ideas

Latest Contributions by MikeMillerGIS

Re: Apply Asset Package FAILED TO EXECUTE

Re: Apply Asset Package FAILED TO EXECUTE

Re: Apply Asset Package FAILED TO EXECUTE

Re: Export Matrix UN tool

Re: Export UN to Mobile Geodatabase

Re: Most current Electric Foundations Data Dictionary

Re: Most current Electric Foundations Data Dictionary

Re: Add Parent Geometry to A Related Record

Re: Junction Edge Connectivity Rules are not enforcing terminal settings

Re: Junction Edge Connectivity Rules are not enforcing terminal settings

Re: DataMapping.xls and Create Migration Workspace - Stormwater vs Sanitary Sewer Foundations

Re: DataMapping.xls and Create Migration Workspace - Stormwater vs Sanitary Sewer Foundations

Re: Utility Network Migration Wizard, Error When Migrating.

Re: Error "The evaluation of attribute rules is cyclic or exceeds maximum cascading level"

Re: Error "The evaluation of attribute rules is cyclic or exceeds maximum cascading level"

Re: Apply Asset Package FAILED TO EXECUTE

Re: Export Matrix UN tool

Re: Junction Edge Connectivity Rules are not enfor...

Re: Attribute Rules - Create Database Sequence

Re: DataMapping.xls and Create Migration Workspace...

European Utility Network Community (UNC)