How do I change configuration to select a project specific border file, rather than a default workspace border while cutting sheets in ORD??

Hi Brett, you'll need to create a new sheet seed dgnlib or copy one from the provided workspace and attach your desired border file. If you have access to your workspace configuration, it could be placed there, otherwise it would need to be placed a project/workset folder. Then you'll see it in the drop down list when in the create named boundary dialog.

Kristina, the OP asked you for the configuration variable that points to the location of the Sheet Seed DGNLIB? What variable tells ORD where to look for those files?

I don't suppose there's any way to Browse to a new sheet seed? Not everyone has (nor should have) the permissions to edit the workspace, and not every workspace is set up where each project has a workset.

I understand that's not how Bentley wants us to work, but real life is far messier and organic.

Brett - one thing you may be able to do is write, or find someone to help you write a VBA routine that you can run after sheet creation that will find the PennDOT border (or an element in the PennDOT border) and attach your border as a reference. I don't know if you use reference borders or active borders. If you use reference borders, you're done. But if you need an active border, once your border is attached as a reference, your VBA could delete all the PennDOT elements, copy the elements from your border through, and detach the reference.

This would be the long way around though.

I suspect the variable you are looking for may be MS_SHEETSEED. Hopefully, someone more certain than I will be along soon.

Hey there, stranger!

In the WorkSet's .cfg file, you can define MS_DGNLIBLIST by appending this variable to also look in a desired folder for the WorkSet itself. I think you may need to also define MS_DGNLIBLIST_DRAWINGSEEDS to look at the same dgnlib. 

For example, something like this: 

MS_DGNLIBLIST  > $(_USTN_WORKSETSTANDARDS)Dgnlib/Sheet Seeds/*.dgnlib

This does require that you setup the sheet seeds per each project, however. That could potentially get cumbersome depending on what you need.

As an alternative, I would offer that you consider doing what FDOT does, which is to utilize fields in the sheet border cells that pull from WorkSet properties (much easier for users to define in the backstage) to help populate the title block information that you need (District, County, Route, Section, etc.). 

I certainly agree with you, eddiegiese. We have an extensive dgnws which is used as a default on all projects and such allows us to reuse our sheets for practically any project. Even our title sheets use this method for populating practically everything on them and then repopulating when used within another WorkSet.

Mark

Thank you for all the responses everyone. 

Eddie, how ya been man?? Long time no speak. Just got reunited with one of our old RETTEW cohorts. Shaun Bentz was just hired in our Mburg office, working hybrid schedule between home and office. Been cool catching up with him. 

Looking at the sheet borders and sheet seeds that PennDOT provides is a little confusing. They include Sheet Seed DGNLIBs, another set of sheet seeds grouped with the design model sheet seeds and another folder with just blank Sheet Border dgns. 

When I run the named boundary tool to cut and create the sheet models, it seems that the border is automatically referenced in from the Sheet Borders folder, not the DGNLIBs. So, would your possible solutions still work?? Kinda seems like I need to revise the variable that sets where the border is referenced from, right?? Maybe I am not thinking about this correct, but the 2 different sheet seed folders and 1 sheet border folder could have me a bit confused. Thanks again for you help.

Brett