Latest Contributions by RobertKrisher

I do not recommend running that SQL statement since it will corrupt the history of the database as well as the network index. If you are a customer who is experiencing this issue, please reach out to support. That statement will corrupt the network index (which references features by their global id) and it will also corrupt the history for the feature because every historical reference for the feature will now have a different global id.   ... View more

If you got that message, it means that all your dirty areas have been validated and you only have errors left so you're good to run the summarize errors tool. The message can be a little confusing, it means that all dirty area features in the extent or database need to be validated. This is because their status is either error or subnetwork error, and none of them have a dirty status (See graphic below):   ... View more

A type 39 error means that you haven't populated the terminal configuration field on the manholes (or it is set to something invalid). Set the terminal configuration on those devices to be default and the error should go away. ... View more

Don't worry about digitized line direction for your water distribution data because flow is derived from your water/pressure sources and these systems are so looped that almost all your flow is indeterminate (so digitized direction is meaningless). For terminal assignments, you just need to make sure you don't have more than one line assigned to the same terminal, and that your upstream terminal always point towards your pressure/water source. If terminals are not properly set you will not get topology errors, you will get subnetwork errors (because pressure zones are interconnected when they aren't designed to be). Sewer/stormwater is a completely different situation. Because these systems are not heavily looped and rely on gravity, customers have historically relied on the digitized direction of lines to manage flow. We will allow you to drive analysis using sources and sinks, but in 3.3 we also introduced an option to trace upstream/downstream using digitized line direction. By default, the utility network doesn't rely on the digitized direction for upstream/downstream analysis, instead it uses sources and sinks. You can deep dive into water modeling on the Learn ArcGIS Utility Network for Water Utilities learning path. ... View more

If your class has subtypes, make sure that you assign the domain to the appropriate subtype as well. The easiest way to handle this is to use the Assign Domain to Field gp tool, since it lets you select all the subtypes at once. ... View more

The relationship isn't strictly necessary, as long as you as you maintain primary/foreign keys. I also discuss the perils of joining your CIS data with your GIS features, exercise extreme caution with this because once you calculate it you need to maintain it (which doesn't work well for large customer bases). A dynamic lookup approach on a well-indexed, non-versioned table is more sustainable for a large dataset. The beauty of popups is that they are configured at the subtype layer in maps, and that they are different for every map. You would only configure the customer information popup on something like a transformer (electric) or service point (electric, gas, water), and not on something like a switch (electric) or valve (gas, water). ... View more