Sheets don't reflect changes to intermediate or master files. - Levels on/off not updating.

I have seen similar questions but the answers all seem to be ridiculous workarounds. It seems like the solution should be simple and straight forward and that makes me think that we are all missing something.

For my project, I set up several “master” files. These include a TOPO, UTILITY and also a CIVIL file. In the end, I need a set of sheets for both the demolition and improvement plan sets.

I set up two “intermediate” files, one for the demolition and one for the improvement, in order that I could set up the individual files to look the way I want all of the sheets to look (layers on/off, line styles and colors).

The intermediate files directly reference the TOPO, UTILITY and CIVIL files.

The sheets each reference the respective intermediate file but this is a nested reference as there isn’t actually any line work on the intermediate (this case “8511_ROAD – IMP.dgn”) files.

All seemed to be going well until I needed to make some changes (including a level name change) in one of the master files and also turn on some referenced levels in one of the sheet files.

No matter what I do in the intermediate file, I can’t get the changes I make to reflect in the sheet files. The only solution seems to be to recreate all of my sheet files from scratch every time I need to make a change.

How do I set up the sheet references so that the levels, colors and Line weights reflect the settings and changes in the intermediate files? How do I set up my sheets so that all the demolition sheets look the same and all the improvement sheets look the same?

Parents
  • One of the settings that can help the reference setting "Display Overrides" set to Never. This does only affect level display, but it can help keep levels on and off at the very least.

    One other thing I have found helpful over the years is to make certain to NEVER turn levels on or off, nor make any other changes to, the nested/container file in the sheets themselves. When a change is made to a container level (nested or not), MicroStation basically switches level control from the container to that sheet. You told it you want to control these levels from the sheet by making that change. Once that happens, changes from the container are no longer reflected in that sheet.

    No, I have never found a good way around it...

    I have seen that I can often "reset" control by turning the nesting for the container file off, exiting the sheet drawing, reopening the sheet drawing and turning the nesting back on for the container reference. It's a couple of steps, but it's often preferable to detaching and reattaching the container entirely. But it doesn't always work...

    There may be other considerations in CONNECT that I'm not aware of...but this behavior has been going on for decades (Works As Designed, if not desired).

    MaryB

    Power GeoPak 08.11.09.918
    Power InRoads 08.11.09.918
    OpenRoads Designer 2021 R2

        

Reply
  • One of the settings that can help the reference setting "Display Overrides" set to Never. This does only affect level display, but it can help keep levels on and off at the very least.

    One other thing I have found helpful over the years is to make certain to NEVER turn levels on or off, nor make any other changes to, the nested/container file in the sheets themselves. When a change is made to a container level (nested or not), MicroStation basically switches level control from the container to that sheet. You told it you want to control these levels from the sheet by making that change. Once that happens, changes from the container are no longer reflected in that sheet.

    No, I have never found a good way around it...

    I have seen that I can often "reset" control by turning the nesting for the container file off, exiting the sheet drawing, reopening the sheet drawing and turning the nesting back on for the container reference. It's a couple of steps, but it's often preferable to detaching and reattaching the container entirely. But it doesn't always work...

    There may be other considerations in CONNECT that I'm not aware of...but this behavior has been going on for decades (Works As Designed, if not desired).

    MaryB

    Power GeoPak 08.11.09.918
    Power InRoads 08.11.09.918
    OpenRoads Designer 2021 R2

        

Children
No Data