Latest Contributions by MikeMillerGIS

‎08-04-2022

Fixing the stacked points probably caused the Error 10s. Make sure the point at the same XYZ as the line has a rule. Check to see if that point is a device and has terminal configurations

‎08-04-2022

For the stacked points, you can offset the Z and leave them stacked on the XY and that will remove that error.

‎08-04-2022

Try running your lines through Repair Geometry. This has an option to remove Duplicate Vertices. This error indicates some of your line features have more than one vertex at the same X,Y,Z.

‎08-03-2022

The terminal id needs to be set on the line class, not the device. If you are trying to create an association, you need to use ^UN_Association https://pro.arcgis.com/en/pro-app/latest/help/data/geodatabases/overview/attribute-rule-dictionary-keywords.htm#ESRI_SECTION1_98D8C1A03B0D4BAB810DCC76DBA88F2C

‎08-03-2022

Can you post a sample dataset with the rule? Couple things: - In this case, I would not call Count. Count can be expensive, as it makes a query to the FS. Best to just call First or loop over the FS and exit on the first record - I do not like reusing the variable parcel to be the FeatureSet and the Feature. Change the first item to var parcelFS - If you right click in the expression, you can turn on line numbers. Will help identify which line has the error

‎08-02-2022

Still working on the online help, but this is the tool - https://esri.github.io/Utility-Data-Management-Support-Tools/docs/2.9/AddUNSystemTables.html

‎07-27-2022

The error is likely because of a duplicate association in your UN. This sound very similar to Bug BUG-000147861. Can you find that feature with the global id? You may have to look at the association table. The UDMS toolset has a GP tool that will generate a view of your association table. Apply a def filter on this using the reported global IDs and see if there is indeed a duplicate association.

‎07-26-2022

I believe the code is correct, but the validation logic is not returning a feature. So you just need to add a check for if stationBoundary is null and that way the validator exits early. Add this under var stationBoundary = First(..... if (IsEmpty(stationBoundary)){ return; }

‎07-20-2022

Should be available tomorrow some time. It will be available via the solution app in ArcGIS Online. 2.9 is the correct version.

‎07-20-2022

If you right click, there should be an option to Check Syntax, that could have told us what was wrong. Either way: The new electric foundation solution is shipping this week and will contain that new toolbox(atbx). That toolbox has a lot of improvements and new tools. That is the right toolbox to use.

‎07-18-2022

The batch trace has the option to store the raw summary results on the starting points. You may have to parse and clean them up, then if you want to store them on downstream features, run another batch trace to push them down.

‎07-12-2022

The solution and tools are not certified on 3.0 and will not be as we are targeting the 2.9/10.9.1 utility network management release. We do have a copy of the tools that are compatible with 3.0 though it you need them. You can find them on our public github repo. https://github.com/Esri/Utility-Data-Management-Support-Tools/tree/3.0 https://github.com/Esri/Utility-Data-Management-Support-Tools/tree/2.9

‎05-31-2022

For a single terminal device, the network attribute will stop traversability(not in a connected trace). If the device has more than one terminal, the network attribute will stop traversability between terminals, but not on the objects connected on the same terminal. I could not locate any doc that provides that info.

‎05-27-2022

Hard to tell what is going on without a sample dataset, but my guess is that the lines at the open device are connected to the same terminal. So opening/closing the switch does not affect the flow.

‎05-25-2022

We went down the same path on xfrs and decided using terminals for the each lug was not worth. You can accomplish the same result with a highside and lowside. As you cannot define attributes on a terminal, what value does modeling each lug and how the wires connect. It is best to detail the wiring as attributes. If you need to model each lug for export to CIM, then additional features are needed, as they each need attributes and a known ID.

Online Status	Offline
Date Last Visited	2 weeks ago

My Ideas

Latest Contributions by MikeMillerGIS

Re: Network Topology Error 21 and 25

Re: Network Topology Error 21 and 25

Re: Network Topology Error 21 and 25

Re: How to set the right terminal when creating connectivity associations with attribute rules

Re: Update point geometry based on polygons centroid

Re: FeatureSetByAssociation function takes only $feature as input

Re: FeatureSetByAssociation function takes only $feature as input

Re: FeatureSetByAssociation function takes only $feature as input

Re: Electric Utility Network Foundation Error in ArcGIS Pro 3.0

Re: Electric Utility Network Foundation Error in ArcGIS Pro 3.0

Re: Using trace configurations in attribute rules

Re: Electric Utility Network Foundation Error in ArcGIS Pro 3.0

Re: The condition barrier does not consider the category value

Re: The condition barrier does not consider the category value

Re: Devices, Terminals and downstream outputs

Re: Problems sharing complex geoprocessing service...

Re: Problems sharing complex geoprocessing service...

Re: Create Simple Data Mapping Errors

Re: Asset Package - Change Asset Type Domain for a...

Re: Pipeline Isolation Subnetwork Confusion

European Utility Network Community (UNC)