We have a project using MicroStation Connect Edition and used OpenRoads for drawing production to create plan & cross sections to specific project folders. I have a workset file that defines the locations of the corridor files and the master compile file that the named boundaries were created in. Our folder structure is as shown in the image below.
The projects base reference files, corridors, etc.. all are stored in the ..02 Draw/01 Production folder, The cross section sheet files are stored in the ..02 Draw/03 Plans/Cross Sections folder.
When I create a PSET, and preview a cross section sheet, the sheet & drawing model contents show up fine, the nested reference of the model does not appear. If the cross section files are in the ..02 Draw/01 Production folder, then the model appears in the sections. I am having similar issues with the plan sheets as well.
If it were an issue with the workset config, I feel like none of the nested references would show up when opening the plan or cross section files. The line character length of each of the file paths is less than 100 characters.
We've used nested references in previous versions of MicroStation hundreds of times with no issues at all.
Any insight is greatly appreciated.
MicroStation Connect Edition Update 13 - Version 10.13.01.01
Are you using ProjectWise?Do you start your workspace using a shortcut that has workspace switches in the target line?In Print Org. have you set the user and project on the advanced tab?
Thanks for the reply Tom,
We're not using ProjectWise.
Currently, I do start the workspace with a workspace switch in the target line and I have tried to set the workset in the advanced tab.
Check out this link:
There's a variable: MS_PLT_ENGINE_CMDLINE_ARGS that you need to set so Print Orgnanizer starts with the same switch as MicroStation.
I didn't think we had to define that variable anymore?
Just re-read your original post - didn't realize you were in CONNECT. I'm still a CONNECT newbie so I can't say for sure. Wouldn't be the first time something didn't work the way it was supposed to.
Just an FYI... Defining the variable did fix the issue... Go figure.
Thanks for your help!!