Remapping from DGNLIB

hello

We have recently renamed all our Level structures and updated our DGNLIBs accordingly.

In the DGNLIB a level that was called say A_AMEN_CLNR is now called ARC_AMEN_CLNR. In our DGN base files pointing to this DGNLIB the level name is A_AMEN_CLNR and when we do an update DGNLIB levels it just bring in all the levels with a the new name. So now we have A_AMEN_CLNR (as a used level) and ARC_AMEN_CLNR as a new level...

Why can in not see that the level has simply been renamed? I see there are a lot of very old posts about remapping levels using a CSV file but its so old and convoluted does it still actually work?

Surely in 2020 we have a better method of remapping than this? Any ideas would be greatly received. I have too many files to try and remap manually.

cheers Kim

Parents
  • You will have to remap the old levels to the new ones. When the element is created, the level used to create it is written to the drawing, and it becomes a local level. It is no longer controlled by the DGNLIB. You can rename the level in the DGNLIB, but that change doesn't carry over to what are now local levels

    MaryB

    Power GeoPak 08.11.09.918
    Power InRoads 08.11.09.918
    OpenRoads Designer 2021 R2

        

Reply
  • You will have to remap the old levels to the new ones. When the element is created, the level used to create it is written to the drawing, and it becomes a local level. It is no longer controlled by the DGNLIB. You can rename the level in the DGNLIB, but that change doesn't carry over to what are now local levels

    MaryB

    Power GeoPak 08.11.09.918
    Power InRoads 08.11.09.918
    OpenRoads Designer 2021 R2

        

Children