With the Connect Edition, how do customize the directory structure that is created when I create a new Workset? I can't find any help on this. With V8i, we have several project template structures setup that we select when creating a new project base on the type of job...Primarily, some complex structures for complex projects and simple structures for simple jobs.
Timothy Hickman
CADD Manager | CADD Department
timothy.hickman@colliersengineering.com
Main: 877 627 3772|
1000 Waterview Drive Suite 201 | Hamilton, New Jersey 08691
Gary Manuel
OBD 2023
Windows 10 Pro
I, too, am interested in setting up a WorkSet Template. I would like to include a few Custom Properties for use with Title Blocks, etc. I would also like to create a standard set of folders. I would also like to specify the location of the main project (WorkSet) folder.
I set up a WorkSet with the custom properties that I want, and I manually added a few other folders (besides dgn, out, and Standards and it's subfolders).
I notice that when I try to use this WorkSet as a template for a new workSet it doesn't allow me to select the folder for the new WorkSet.
At the very least I would like to standardize the Custom Properties across any new WorkSets. So far I have just created Worksets with no template. I then manually added in the other necessary folders.
Can I do any or all of this with a WorkSet template?1. Define Custom Properties2. Create a folder structure that includes folders outside of the Standards folder3. Choose the location of the WorkSet folder?
Thank you.
Using Method #2 as I described above you can accomplish items 1 & 2.
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
Rod WingSenior Systems Analyst
Thank you. I will look into this. But it raises a bigger-picture question:
We use the same exact standards for all of our projects. We are a local government engineering office producing plans for our own use. We don't have different client workspaces, etc. The only benefit of using WorkSets is the use of a dgnws file. Is there a reason I can't just use the same WorkSet for all projects? I have only created a dozen or so WorkSets so far, but as I create more and more over the next few years the drop-down list of WorkSets is going to get annoyingly long - all using the same standards other than maybe a local template library.
In SS2 all users used the same Project and Interface for all projects, but and our own User..
That's a common concern for a lot of companies. We have numerous clients that are just using the one WorkSet for everything model.
There are three drawbacks to going with a single WorkSet
Josh M said: I would like to include a few Custom Properties for use with Title Blocks, etc.
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.
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.