ORD Connect 2020 Release 2 Update 8 - Version 10.08.01.33
I have been following the Bentley Learn link for "Under the Hood - Setting up Sheets - Part 1 and 2" to set-up our sheets for the first time.
Iv'e created my Drawing Seed, Sheet Seed, Border Drawing, my config variables point to the correct seed files, and I'm using my dgnlib file to create my Named Boundaries.
When I get to the Create Drawing dialog, the OK button is grayed out and the Drawing Model>Seed Model: in listed is red, hovering over it doesn't give me any info on the error. See attached.
What is the error about? The seeds are listed properly in my config file.
Primarily, the configuration variabes are seen at C:\ProgramData\Bentley\OpenRoads Designer CE\Configuration\Organization-Civil/_Civil Default Standards - Imperial.cfg. More specific civil variables are found in the workspace config file (C:\ProgramData\Bentley\OpenRoads Designer CE\Configuration\WorkSpaceSetup.cfg
Yes, but I've modified my Civil Organization Root in my WorkSpace.cfg file to point to a server, I have 3 other CAD users. So it all points to my modified standard workspace. This is probably the root of my issues. But all was working great, until this roadblock.
Assuming that you DID NOT modify any other config variables other than the MY_CIVIL_ORGANIZATION_ROOT path and the MY_WORKSPACES_LOCATION path, everything else should have synced up just fine; at least, all worked well for me as it is merely a copy of the local delivered configuration hooked to a different location. CIVIL_ORGANIZATION_ROOT in situ has no need to be modified as MY_CIVIL_ORGANIZATION_ROOT = CIVIL_ORGANIZATION_ROOT when utilized/ pathed.
Yes, correct, but I did, however, also modify the Workset location to reside in the same directory as the rest of our library of previously created dgn files.....at the time I thought that this was what I was supposed to do. I thought the Worksets had to reside with the dgn's. I did this using the guidance of a Network Workspace Set-Up pdf that I downloaded from the Learn Server. I never quite grasped the need for the Worksets....we are a municipality, our design standards, units, nothing, changes from project to project.
Maybe this is where my issues are....
I merely treat the worksets as an extension of the old *.pcf file, You can actually store them wherever you want by the use of the MY_WORKSET_LOCATION configuration variable within the WorkSpaceSetup.cfg file. You will need at least one workset in order to have something underneath your Workspace to grab. Good for you it has no need to change! Since you have a decent grasp of the variables involved and what they do, you might just run a do-over to straighten stuff out?