Hi,
this question is a consequence of thinking about an issue discussed by Rod Wing in this post.
To refresh my knowledge, I read these two wiki articles about level numbers:
Both articles are based on two basic rules: Every level has a number (at least internally) and the number has to be unique in a context of the file.
So I did some tests using example(s) delivered with MicroStation CE U13.1 installation (_USTN_CAPABILITY < +CAPABILITY_LEVELS_USE_AUTO_GENERATED_NUMBERS configuration added to standard.cfg to see the auto-generated numbers) ... and I am confused:
In GrazURL.dgn, an initial state is:
Situation: There is no conflict in numbers, but it's visible that a threat exists, because GrazRoads and Interior Floors both have auto-generated numbers *3*.
The next step is to place an element to Interior Floors, when the level definition is copied to active design file, which requires to solve the numbering conflict. The result is:
I used VBA to check level internal IDs and they are fine, only numbers are in conflict.
Is it bug or I do not understand the mechanism and rules right?
I did not do any test using V8i, so I do not know whether the result is the same or different, my test was more about to understand how MicroStation CE behaves.
With regards,
Jan
I remember similar issue was when upgrading from v7 to v8 that auto-numbers also used numbers 1-63 which was problematic.
I remember that...
MaryB
Power GeoPak 08.11.09.918Power InRoads 08.11.09.918OpenRoads Designer 2021 R2