Latest Contributions by RobertKrisher

The digitized direction of the sewer system will be more reliable since the digitized direction of mains typically indicates flow with respect to gravity. he same can't be said for water, where the system typically operates under pressure and is highly looped. It would be nice if the edges were always drawn to indicate upstream/downstream, but I suspect in many datasets this is not the case. That's my long-winded way of saying I would honor digitized direction for sewer but not for water. Once you create a subnetwork (water treatment plant, wastewater treatment plant) and run update subnetwork, you'll be able to see whether you've flipped any terminals because features will be disconnected. Once you create pressure zones (w) and subbasins (ww) you may find that some of your networks are interconnected (inconsisent subnetwork name) because two pipes share the same terminal on a valve. ... View more

Removing the second rule is a bad idea and you should roll it back immediately. That would connect all the valves to the same port, which means that the flow valves can't control flow and operable valves can't close (because water isn't flowing through them). Take a look at this thread for how to access a tool to populate terminals en masse. ... View more

We don't allow you to make the rules not fire, but you can create 'early exit' conditions that allow the rules to exit before they do any heavy analysis or editing. We have an item on our roadmap to allow you to refine when attribute rules so certain rules will only be triggered when specific fields are edited. ... View more

@PierreloupDucroix the two classes are the same instance of the same class. The underscore indicates that it is an internal variable that you shouldn't be using. The API does have a certain amount of flexibility with handling different URLs. I have made note of the issue with the documentation and forwarded it to the team responsible for maintaining the online help. ... View more

@PierreloupDucroix You will need to include your condition barriers as part of your trace configuration object and because the trace configuration object in ArcGIS API for Python is a 1:1 match for the rest spec object you need to make sure your key names match the rest spec: conditionBarriers, incluseContainers, etc ... View more

Dirty areas from within your version are posted to default (so we can restitch the areas modified in your version), can you confirm that the unique constraint that is being violated includes global id, gdb_branch_id, and gdb_from_date? If you haven't already opened a support case for this issue, I would recommend you do that (getting a global id constraint error on post is a sign of something not good happening). The app lock error for validation network topology is likely being caused by something else validating/enabling/disabling the network topology in that version. Make sure you don't have any other scripts running or people validating default, wait 15 minutes for the lock to time out, and try again.   ... View more

@PierreloupDucroix  Does this script work when you run it in a CONDA prompt and fail when you run it in a GP service? I just tested this locally with ArcGIS Pro 3.3 and ArcGIS Enterprise 11.3, and when the logged in user didn't have the ArcGIS Advanced Editing user type extension assigned, I would get this error, but as soon as I assigned it to the user the tool would succeed. I'll wait for confirmation from you before I dig into testing this with a GP service.     I agree that the error message can be misleading because it sounds like you're missing the utility network user type extension, when instead the service is saying you're missing the user type extension required for the utility network (which was previously a un user type and is now the advanced user type). ... View more

If you look at the same FGDB using ArcGIS Pro 2.9.5 does the data appear correct if you add the data to a new map in ArcGIS Pro? Upgrading your ArcGIS Pro shouldn't affect the data that is stored in the database. ... View more

If you're working through a lot of errors/dirty areas, I recommend you validate your entire topology and run the Summarize Utility Network errors tool (part of the data management support tools) to look at your errors. You can find an overview of the data migration and cleanup process in video form here (including what I described above): Running a successful Utility Network Prototype  Water Topology Error Tutorials here: Managing Connectivity with ArcGIS Utility Network  Water Article here:  Water Topology Errors  ... View more

That blank field is usually a sign of default values not being populated when the feature was converted. So anywhere else you see a 'type 39' error in your database you should double check the other fields like lifecycle status and normal position to ensure they have the correct value. Also, if you're still working on a data conversion, make sure you update your data mappings/migration to handle this. ... View more