Workset Templates

One more thing that I forgot...

If you are using OpenRoads Designer, many companies like to have a project-specific template library (.itl file). You really can't set that up if you're using one WorkSet for everything.

Thanks, Rod.

Since I would like to use custom properties and project-specific template libraries I think I will continue to use separate worksets for now.

I also would like to use a template but be able to specify where to create the folder structure.  If I don't use a template I can specify where to create the folders (anywhere on the server).  When I use a template the folder location options are greyed out..  Workset 3670 was created in a completely different folder on a network drive.

In my WorkSet template I set up a folder structure similar to the image on the left.  I would like to able to use this folder setup when creating a new workset from this template.  Up until now I just added the other folders manually after creating the Workset.  Is it possible to do what I am asking?  Like I said, when using a WorkSet Template the root folder option is greyed out.

Rod Wing said:

The WorkSet template must reside in the folder where your new WorkSets will be created. You can change the location by modifying the variable _USTN_WORKSETSROOT

You cannot separate the template WorkSet from your production WorkSets. They must be in the same folder defined in the _USTN_WORKSETSROOT variable.

My WorkSets are stored in the default location set by the out-of-the-box _USTN_WORKSETSROOT variable.  I have not changed it in any other location.  However, at the time of a WorklSet creation I specified the location of each Workset (the Root folder).  This results in a cfg and dgnws file being created in the WorkSetsRoot folder, but the project folders (dgn, out, Standards, etc.) are stored in the proper locations on the server where everyone is used to finding them.  ORD adds the following line to the end of the WorkSet's cfg file to point to the "real" location of my project's files:

_USTN_WORKSETROOT = F:/Home/PW/CAD/FILES/3000_Streets/$(_USTN_WORKSETNAME)/

I noticed that are two dgnws files:  one in the WorkSets folder and one in the project's Standards folder.  I imagine this is going to create some problems somewhere down the line.  I just don't know how, when, or where.

My WorkSets are stored in the default location set by the out-of-the-box _USTN_WORKSETSROOT variable.  I have not changed it in any other location.  However, at the time of a WorklSet creation I specified the location of each Workset (the Root folder).  This results in a cfg and dgnws file being created in the WorkSetsRoot folder, but the project folders (dgn, out, Standards, etc.) are stored in the proper locations on the server where everyone is used to finding them.  ORD adds the following line to the end of the WorkSet's cfg file to point to the "real" location of my project's files:

_USTN_WORKSETROOT = F:/Home/PW/CAD/FILES/3000_Streets/$(_USTN_WORKSETNAME)/

I noticed that are two dgnws files:  one in the WorkSets folder and one in the project's Standards folder.  I imagine this is going to create some problems somewhere down the line.  I just don't know how, when, or where.

There are a lot of companies that want to do exactly what you are doing when creating new WorkSets, put the .cfg in one location and the dgn's in another. There is no way using the MicroStation delivered WorkSet creation options to do this in a more automated fashion. You have to manually change the folder paths as you are doing. That is why some clients have asked us to create a custom WorkSet creation tool. Due to the issues of renaming the .dgnws file this cannot be done either. 

Speaking of the .dgnws file, and your duplicate copies. MicroStation will only use the one defined by the _USTN_WORKSETDGNWS variable.

Thanks for the help with the duplicate DGNWS files.  It's of little comfort to hear that others are experiencing some of my frustrations with this software.  I guess it shows me I'm not the only one.