Hello,
Upgraded to Pro ver 3.5.2... Just tried the tutorial "Utility network migration wizard walkthrough" (https://www.esri.com/arcgis-blog/products/utility-network/water/utility-network-migration-wizard). I chose stormwater ("sink" as controller type, "hierarchical" as tier definition); chose asset types the same as the tutorial screenshot - although the chosen asset types didn't show up in the summary. My service territory FC is the only thing I added from my existing data.
When I clicked "Finish", I immediately saw "Error 00800: The value is not a member of StructureJunction | StructureLine | StructureBoundary | SinkDevice | SinkJunction | SinkLine." When I closed the error window, "Migrating" window was still running, but disappeared after 2 seconds or so.
Anyone experiencing the same issue, or could explain what I did wrong? Greatly appreciate help!
Solved! Go to Solution.
I've gotten the same error when the "Name" field was left blank. Go thru the steps again and make sure that field is populated.
Step 4 of the article says that you must populate the Name, Source Type, and Tier Definition. The issue is that there is a bug (that we're waiting to patch) that lets you proceed to the next page without populating the Name field on the domain network.
I have added a note to the article that explicitly reinforces this, along with suggestions for the domain network name to use in each example.
@NobukoConroy_BFS - The target class needs to one of the values highlighted in the error. StructureJunction | StructureLine | StructureBoundary | SinkDevice | SinkJunction | SinkLine
It's failing to recognize the values of "Device" etc where it is expecting the value to be "SinkDevice"
The tutorial screenshot.
I've gotten the same error when the "Name" field was left blank. Go thru the steps again and make sure that field is populated.
Step 4 of the article says that you must populate the Name, Source Type, and Tier Definition. The issue is that there is a bug (that we're waiting to patch) that lets you proceed to the next page without populating the Name field on the domain network.
I have added a note to the article that explicitly reinforces this, along with suggestions for the domain network name to use in each example.
Thank you @RobertKrisher, I missed that instruction! Greatly appreciate your reinforcing that part for a newbie like me.
No problem! We've gotten some good feedback on the tools since they were released, and are hoping to include some bug fixes to tighten up some of the error handling/validation of the tool to help users spot these issues before they run the migration.