No more bits for in line network attribute

[PierreloupDucroix]

Hello,

I'm trying to add a network attribute inline, but I'm getting the following error:

Error 001953 The length of the selected domain exceeds the number of bits remaining for the inline attribute.

Indeed, it seems that I've reached the 25-bit limit for user-defined attributes in my UN:

How can I get more bits, either removing a network attribute, or removing the "In Line" properties if possible.

Thanks

[PierreloupDucroix]

Alternatively, is there a way to upgrade the number of bits used by an attribute ?

What I want to do, at the end, is adding some values to a domain that is assigned a network attribute.

Currently, the attribute uses 4 bits (7 values), but adding these values will need 5 bits (10 values).

[gis_KIWI4]

If you have 10 values in the domain then you should be able to fit that into 4bits? Or did you mean 10 additional values to the current domain? 

[PierreloupDucroix]

You're right, it was 0 to 7, so 8 values, then 4 bits.

I changed the domain and now I have 0 to 10, so 11 values, which should still use 4 bits, but when I try to add to a field that has the network attributes I get the error:

ERROR 003856: The max value of the domain exceeds the bit size of the network attribute.

This is why I tried to create a new network attribute, but now I am stuck with the total number of available bits...

[JohnAlsup]

You will want to have the network attribute inline if it is used in the subnetwork definition, as not inline requires more queries and could have a significant impact on performance.

Also, what bit are you planning to add.  I'm guessing this is electric.  Adding more bit to phase may get very complicated.  For example, there is no way to represent phase orientation with this field.  Also, if you are trying to include something like Neutral as a bit or static wire, that also will get very complicated.  

[PierreloupDucroix]

All the inline attributes are used in the subnetwork definition, not for traversability, but for summary purpose. Is it necessary to store them inline in this case ? I cannot find a good documentation about this.

Any way, do you know why I cannot add values to my domain while respecting the same number of bits (from 8 to 11 values) ?

This is not for phase propagation but for voltage. It was intended to be used only for MV, but we know want to include some LV values and use the same domain for LV network voltage propagation.

[EstherSmith_Dev]

Hi @PierreloupDucroix ,

You can un-inline some network attributes to make way for new network attributes.

It is not required to have every network attribute defined as "in line". The network attributes that define subnetwork (condition barrier) such as "Life Cycle Status", "Open/Close/Operational Status" etc. should be inline.

If you have certain traces that use aggregation or filter barriers using network attribute they can be added as in-line for the performance reason. I would leave out network attributes that are rarely used in traces from to being inline.

Cheers,

[PierreloupDucroix]

Thanks,

could you tell me how to un-inline attributes ?

Because I cannot find a way.

[MikeMillerGIS · Accepted solution]

Sadly, Asset Package is the only way

[PierreloupDucroix]

Arf... this is bad news, is there a plan to include network attribute deletion or the capability to un-inline attribute ?

Going back to an asset package would mean loosing versions and a lot of archived data, it is not an option for production.