I am having trouble setting up the workspace and worksets for our company. I moved the configuration folder to our "T" drive but I am having trouble setting up the worksets for each project considering the layout of our drive. We use different folders for each project and I am wondering if there is a way to make a workset for each of these while still using the same "standards" from the workspace. I have attached an image to possibly help with understanding the way our layout is. I have examples of our project folders and then the configuration folder on our "T" drive.
Also when a new workset is created is there any way to make it use the same standards that are already set up in our workspace folder or do they have to be copied for each workset.
Here is a list of blog articles that have some useful information about setting up workspaces, worksets and network resources.
There is also an entire forum dedicated to Product Administration that has a lot of additional information.
I have the C:\ProgramData\Bentley\OpenRoads...\Configuration\ directory structure duplicated on my network CAD standards drive.
This means that, as long as I can redirect the root folders, the rest of the paths stay "relative" and essentially unchanged. I have pulled the worksets out to their own directory because of the way we store our data, and the need for the workset DGNWS file to have write-access.
I use a combination of C:\ProgramData\Bentley\OpenRoads...\Configuration\WorkspaceSetup.cfg and ConfigurationSetup.cfg to handle that basic redirection. I still have a few kinks to work through, but it's functional.
Workspaces and configurations are definitely different than they were for decades.
MaryB
Power GeoPak 08.11.09.918Power InRoads 08.11.09.918OpenRoads Designer 2021 R2
I got it to work how you both mentioned earlier! Thanks for all the help!
The capability mentioned in Paul Cusack's reply can be combined with the built-in workspace capabilities, to get Project Folders working in multiple locations. To accomplish the same thing in V8i took a lot of manual customization of many CFG files. At the other firms I worked, we generally had one person create the Project files on the network for everyone to use. While it might be possible to allow any user to create projects in the workspace, the steps necessary to accomplish this and to maintain uniformity and consistency might be too much to expect.
Charles (Chuck) Rheault CADD Manager
MDOT State Highway Administration
I did both of these things and set up the configuration setup and the workspace setup on my local drive to direct it to the "T:\Configuration\Organization-Civil" folder but anytime I make a workset that doesn't also have all of those folders/files from the Standards in the "Organization-Civil" folder, none of our levels or anything are in the dgns that are created.
The Organization-Civil folder an contain multiple Agency/Client/Whatever folders for as many different standards as you need. You can then define the variable CIVIL_ORGANIZATION_NAME to match the folder name and CFG filename stored in that folder, in the Workspace CFG file that the menu's call. These can be local folders or a network share.
Additionally, once you move to ORD 2022 R1, the startup screen (or backstage after pressing Close (Ctrl+W) supports multiple configurations in multiple locations.
We place most of our main workspace files in that main folder under Organization-Civil and while there is an entire folder structure under our WorkSpace for additional settings, we do not store many things in that structure.
Workspaces are very different than prior releases, so even those of us that knew and understood CFG files "like the back of our hand" find ourselves having to relearn a lot. The changes with 2022 R1 are nice but did change how a number of things worked prior to it, so even that caused a few hours of head scratching and testing before I was comfortable with their new operation.