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.
As per the screenshot , Please select the seed file and make sure that the seed file is located in the workset folder, That means please make sure that you are in active workset to deliver the sheet from created Drawing seed .
Regards,
Avdhoot
For more information about the Road and Site design tools, visit the Road and Site design WIKI at: http://communities.bentley.com/products/road___site_design/w/road_and_site_design__wiki
I am creating my drawing seed, not using it. There is no option to pick the Drawing Seed Model - it's populated by my config file, right? The Sheet seed model seems fine (populated using the same config file). I realize that this is probably a workspace/workset or a naming/lingo issue, but I don't even know where to start looking. I am coming from SS4 and Geopak, and never set anything up previously. I guess I need some person to person guidance, because I've watched so many videos about the same thing and still can't get it.
Steves:
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.
Mark
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....
Yes, possibly...
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?
There are sheet seed DGNLIB's in our ORD workspace that Chuck Lawson help us setup. They are pointed to by MS_DGNLIBLIST which says is for the following:
List of DGN library files that are used to find Levels, Line Styles, Text Styles, Dimension Styles, Multiline Styles, Element Templates, Text Favorites, Table Styles, Report Definitions, Drawing Seeds, Drawing Boundaries, Display Styles, Display Rules, Page Layouts, Saved Views and Item Types for your current session. (MS_DGNLIBLIST)
I am not 100% sure how this works with seed dgn files, but this was a key process according to Chuck.
Charles (Chuck) Rheault CADD Manager
MDOT State Highway Administration Maryland DOT - State Highway Administration User Communities Page
We were facing a similar issue with our workspace a couple of months ago. The filename shown in red was deceptive, as the problem was not with that seed file path. We did manage to resolve it after about a month of head scratching.
Do you have a variable MS_DGNLIBLIST_DRAWINGSEEDS defined? We have that pointing to our directory of DGNLIB seeds. We commented out the entry for MS_DGNLIBLIST pointing to our DGNLIB seeds. I don't remember for sure, but this might have been what fixed the issue for us.