searching feature definitions

Hi Katie

One way to limit your choices when searching the feature definitions would be to set up separate worksets, each with reduced dgnlib libraries better suited to a particular project or workflow.

To make sure only the streamlined dgnlibs are being loaded for a given workset, check the CIVIL_CONTENTMANAGEMENTDGNLIBLIST system variable that defines both the directory and specific file name of the feature definitions DGN Library. You can access the variables manager by typing "configuration variables" in the search ribbon

docs.bentley.com/.../Configuration2.html

The Variables manager only edits the Personal.UCF by default, doesn't it? That's not going to help with a workset.

Are you suggesting multiple worksets for a single project? How would that work for plans integration, with a handful of sheets in one workset, a handful of sheets in another workset, and even more in a third workset? All in one project? What happens when the drainage folks need access to the roadway drawings? or the traffic guys need them both?

With workset "Branding", there isn't a choice to open files with the current workset - The only choices are to open the drawing's workset, or use "No Workset". How does that work with multiple worksets on a single project?

Where is the IDEAS forum for OpenRoads? I would like to submit a request for Feature Definition Searching.

Hi Mary

Not really, creating multiple worksets for a single projects would not be practical - I was rather suggesting streamlining the dgnlibs available for any given workset, so that they meet the needs of a particular project. That way you won't be loading all of your company standards (through the paths defined in CIVIL_CONTENTMANAGEMENTDGNLIBLIST) for every single project, whether you need them or not. Controlling these paths will help you declutter feature definition search and selection.

We setup a detailed tree structure in our Feature Definitions with Geometry as one of the main branches. This can lead users to defined subsets of Feature Definitions for specific purposes. Would an approach like this work for you?

I would venture to say that a custom configuration for each project is even less practical then would be multiple WorkSets for a project. So, let me make a request that an enhancement be filed for a better interface for selecting Feature Definitions that would also include the ability to search, sort and filter.