Utility network error codes

[OliviaGill3]

Why are certain error codes not present in the full list and just refer to 'Unknown' (see the list below) . They are missed in the documentation also ie. 14: unknown Is this a reference to them being based on bitwise values?

 "12: " + unknown, 
                       "13: Midspan connectivity not allowed.", 
                       "14: " + unknown, 
                       "15: " + unknown, 
                       "16: " + unknown, 
                       "17: No containment rule.", 
                       "18: No structural attachment rule.", 
                       "19: Multipart line encountered.", 
                       "20: Self-intersecting line.", 
                       "21: Duplicate vertices.", 
                       "22: " + unknown, 
                       "23: The subtype or the discriminator are out of range or the combination is invalid.", 
                       "24: Invalid line feature was discovered during updating subnetwork.", 
                       "25: Stacked point features.", 
                       "26: Invalid device feature was discovered during updating subnetwork.", 
                       "27: Invalid parent subnetwork discovered during update subnetwork.", 
                       "28: Disjoint subnetwork discovered during update subnetwork.", 
                       "29: Inconsistent subnetwork name on multiple subnetwork controllers in the same subnetwork discovered during update subnetwork", 
                       "30: Inconsistent subnetwork name on multiple parent subnetwork controllers in the same subnetwork discovered during update subnetwork.", 
                       "31: Association record is referencing an invalid from or two globalid.", 
                       "32: Error setting weight values.", 
                       "33: Inconsistent asset group or asset type of subnetwork controller discovered during update subnetwork", 
                       "34: Feature or object in unsupported containment relationship", 
                       "35: Feature or object in unsupported structural attachment relationship", 
                       "36: Line feature has invalid terminal", 
                       "37: A feature with the Subnetwork Tap category was found midspan to multiple lines.", 
                       "38: Devices with multiple terminals cannot be midspan.", 
                       "39: Point feature has invalid terminal configuration", 
                       "40: Invalid junction feature was discovered during updating subnetwork.", 
                       "41: Invalid junction object was discovered during updating subnetwork.", 
                       "42: Invalid edge object was discovered during updating subnetwork.", 
                       "43: " + unknown, 
                       "44: " + unknown, 
                       "45: " + unknown, 
                       "46: " + unknown, 
                       "47: " + unknown, 
                       "48: " + unknown, 
                       "49: " + unknown, 
                       "50: " + unknown, 
                       "51: " + unknown, 
                       "52: " + unknown, 
                       "53: " + unknown, 
                       "54: " + unknown, 
                       "55: " + unknown, 
                       "56: " + unknown, 
                       "57: " + unknown, 
                       "58: " + unknown, 
                       "59: " + unknown, 
                       "60: " + unknown, 
                       "61: " + unknown, 
                       "62: " + unknown, 
                       "63: " + unknown]; 

[JoaquinMadrid1]

Hi there... I do not have a straight answer to your question. Yet, I hope my comments below are helpful.

When we analyze Dirty Areas, besides checking the Error(s) field of the polygon in a pop-up (for example... 9: Invalid connectivity - More than one junction edge rule applicable.) we also focus our attention on the Error Code. This field, seemingly a bit-wise code, provides additional information that helps us analyze the error. For example, Error Codes 256, 512 and 768 (x100, x200 and x300) are all three about Invalid Connectivity, but with slightly different "flavors":

Although not limited to this use case, we found this technique particularly useful when analyzing the results of a migration. Change the default symbology of the Dirty Areas to be driven by Unique Value Error Code and show its count as well. Represent the Error Code in its hexadecimal format and you start seeing the patterns as the bits shift left. Another example? Stacked Points, or the x0200 hhhh series:  

[JoaquinMadrid1]

Oops, I just noticed that in the last example, Stacked Points, I forgot to add the first of the "series":

Cheers.

[RobertKrisher · Accepted solution]

The codes that are showing as unknown in that list are either error codes that have been deprecated, or codes that have been reserved for future use. Because of the way that the arcade expression has to parse out the bits for each error code the lookup must contain all past and future codes to support backward and forwards compatibility.