I am trying to analyze and troubleshoot some workspace issues. Some of these are stored in a location that is accessed using the Custom Configuration options. Haw does one get the Configuration Explorer to include any Custom Configurations?
My understanding was that any application that has your workspace accessible from within the software should show them listed in Configuration Explorer. If this is not the case with your configuration would you be able to provide more details as to how they are being configured.
RegardsAndrew BellTechnical SupportBentley Systems
Another alternative may be to created a debug and open this in Configuration Explorer
CADDCOP, What type of Custom Configuration are you trying to add? Do you have .cfg files that you are looking to add to a workspace, or a .dgnlib? What files are you attempting to modify?
I guess a workflow of where you started and what your desired end result may help in solving the issue.
Power InRoads v8i 08.11.09.615
Microstation CONNECT 10.15.0.74
Microstation v8i SS 10 08.11.09.919
ORD CONNECT 10.9.0.1
ORD CONNECT 2021 R1 10.10.1.3
One of the features you can implement is to use the Custom Configuration capability to allow the delivered and locally stored workspaces in the Example Configuration area while in the Custom Configuration, Show a network (or other) configurations. This might be different in the newest release of ORD or MicroStation, but I am stuck with ORD 2020 R3 (Update 9, I believe).
I was able to load an msdebug.txt file, but I think I need to add some command line switches to force workspace and worksets to get a full picture.
Now what we need is a similar tool for Managed Workspaces in ProjectWise. Its output is still to much of a black box.
Charles (Chuck) Rheault CADD Manager
MDOT State Highway Administration
I also discovered if the last session used a custom configuration, the configuration explorer finds them!
And the msdebug.txt helped me find a error in processing order. I located one file in a bad location which cause my workspace.cfg file to be read three times - once as organization, once as system and finally once as workspace. It helped me determine how to fix it.