Good morning. I am working on migrating our firms v8i workspaces to the CONNECT edition. With v8i we have USERS that correspond to our clients, usually a DOT and PROJECTS that correspond to different versions of DOT workspaces we need to sometimes use for working with our subconsultants. Each PROJECT has different STANDARDS files for each subconsultant WORKSPACE. When I use configuration migration for CONNECT to attempt to convert these .UCF and .PCF to the WORKSPACE.CFG and WORKSET.CFG files, the standards are automatically stored based on the WORKSPACE itself rather than the WORKSET. For example, I set up a WORKSPACE called XXDOT, and a WORKSET called DOT_2017 for the version of the workspace we want to use. However, the STANDARDS seem to be tied to the XXDOT WORKSPACE rather than the WORKSET. This will not work for us since each PROJECT/WORKSET will need to use diff STANDARDS. The only solution I see is to create a separate WORKSPACE for each of our old .PCF files, rather one WORKSPACE from .UCF with multiple WORKSETS based on our .PCF files? Is there a way to set the diff STANDARDS to work with the WORKSET?? Hopefully that makes sense. Thanks.
Hi Brett,
The migration wizard attempts a best fit reflecting the V8i configuration.
You may be better off with a manual approach. There are Standards folders in both WorkSpace and WorkSet structures, Out of the box configurations look at both and pick up any content placed in them.
It sounds like some manual transcription of variable statements from your UCFs to WorkSpace CFGs and from your PCFs into WorkSet CFGs would give the required result, Would you like to post a couple of existing UCF and PCF examples here for further comment?
V8i variables such as _USTN_PROJECTDATA generally map to _USTN_WORKSETSTANDARDS, and so on.
There is a lot of information in our blogs: Configuration Blogs TOC - MicroStation Blog - MicroStation - Bentley Communities
Is this just MicroStation or other products such as OpenRoads?
Marc