I am still trying to wrap my head around worksets. I can get this far:
MY_WORKSET_LOCATION = S:/Project Files/_USTN_WORKSETSROOT = $(MY_WORKSET_LOCATION)
I have a few problems, because this isn't quite right.
Our projects (which I envision to be our worksets) are actually stored in
S:/Project Files/2019/S:/Project Files/2020/S:/Project Files/2021/and so on.
This is regardless of client, department, etc. Everybody's projects go into this structure by project number which is year-project so that each project has its own set of subdirectories. I am not going to be able to convince the entire company to change how we store projects because the transportation department is switching to OpenRoads.
In addition to this, I'm probably going to have to back into our worksets because that directory structure is going to exist for a couple months before I get involved into the project. All of the administration, contracts, proposals and other front office work that go into that project get set up before the actual CAD starts up.
What's the best way to manage this, from a configuration standpoint?
I've been through this situation with several clients.
The solution we find to work best is to keep the WorkSet .cfg and .dgnws files under the default WorkSpace folder structure, then store the dgn files, plot files, etc. in your company specific project file structure.
I first create a WorkSet Template and reference them using_USTN_WORKSETTEMPLATE _USTN_WORKSETDGNWSTEMPLATE
The template .cfg file has custom lines I place at the beginning, something like this....
MY_PROJECT_LOCATION = S:/Project Files/MY_PROJECT_YEAR = YYYY
_USTN_WORKSETDGNS = $(MY_PROJECT_LOCATION )$(MY_PROJECT_YEAR)/$(_USTN_WORKSETNAME)/
When you create a new project using the template you have to edit the MY_PROJECT_YEAR variable to reflect the correct year.
If all of your new WorkSets are going to be 2021, then just use that value in the template and you don't have to change it until next year.
Rod WingSenior Systems Analyst
Answer Verified By: MaryB
that means she needs a workset for every project - all you are doing is saving the user browsing to open a file.
She stated above that the configuration is the same for all projects (per client).
Timothy Hickman
CADD Manager | CADD Department
timothy.hickman@colliersengineering.com
Main: 877 627 3772|
1000 Waterview Drive Suite 201 | Hamilton, New Jersey 08691
Yes, that is true.
If you want to get into using the Sheet Index, and using custom WorkSet properties on your sheet borders and title blocks then one WorkSet for every project is a must.
wellll we could go further and say - if the project is split between disciplines and each discipline needs its own sheet index, then the project could require multiple "worksets" since only a workset can have a DGNWS.
Yeah...I'm not going that far at this point. I need to get transportation up and running before I move into anyone else's space. After I've got my configuration working on a macro level, I can dig into the finer properties of all the settings.
MaryB
Power GeoPak 08.11.09.918Power InRoads 08.11.09.918OpenRoads Designer 2021 R2
You are correct, and that can be a problem.
It is probably one of the biggest problems (of which there are many) with the Sheet Index as it is currently delivered.
Fortunately, most of our clients don't get down to that level of granularity in ORD.