Exactly what John is saying... if you want to combine Domains, their Service Territory mut be the same.
Let us think about it... The Service Territory, or whatever you want to call this polygon, is simply an artifact with two simple jobs:
- Use its Spatial Reference to create the target Dataset
- Use its extent (actually a buffered envelope) to define extend of UN validation.
Let me explain... once you create an E-GDB to host your UN, I do recommend, like most folks, that you use the Esri Foundations to get going. Therefore, you use Esri Solutions' Utility Network Package Tools to:
- Stage UN
- Apply Asset Package
And that is all good, but... If you want to understand what is involved in a UN implementation, I encourage you do everything from scratch... just as an exercise.
Once the E-GDB is created, and using Data Management Tools, execute
- Create Feature Dataset <- providing a Spatial Reference
- Add New Feature Class - polygon (call it, for instance, Service Territory) with GLOBALID and M-value
- Create one polygon feature by editing its geometry (which derives from the Spatial Reference used to create the Dataset)
It is at this point that you, from the Utility Network Tools, you would run
- Create Utility Network - providing as input the just created Dataset and the polygon feature class
As a result, a UN is created containing all the UN internals plus its single Structure Network (SJ, SE, SJO, SJO).
At this point you run
- Add Domain Network - for each domain in your UN (in your case Water and Sewer)
Since the input parameter is THE UN just created, your domains inherit the UN's Spatial Reference as well as the validation extent defined by the polygon.
And that is why, if you were to apply different APs to the same target E-GDB UN... the APs must have the exact same polygon under the exact same Spatial Reference.
