[CONNECT] Workspace without WorkSets

Hi, I'm new to CE and try to migrate our V8i workspaces to CE. It's clear that old site level now is organization. And from my point of view our old project level now should be "Workspace" level, because it contains client resources. It seems that Bentley agrees here.

The issue for me is: We have many small jobs (resp. sets of DGN) for each client (resp. Workspace). Each job needs the same client resources and nothing extra. Though the Workspace/client resources are needed to edit or view the DGN files, none of these DGN files belongs to the Workspace. The design files are stored anywhere on the file system, but never inside microstation's WorkSpace. And that's why the WorkSets seem to be useless in our work flow. Unfortunatly I can't see a way to open a design file with specified Workspace but without a WorkSet. When I use a configured dummy WorkSet, it often stands in the way: The opened files are marked with WorkSet name, causing confirmations about WorkSet mismatch...

Hope, someone could tell me, how to get rid of WorkSets or at least the nasty side effects (I cant imagine that our work flow is that uniqe).

Thanks, Robert.

Parents
  • And from my point of view our old project level now should be "Workspace" level, because it contains client resources. It seems that Bentley agrees here.

    This is not a correct statement. The project in V8i would be your workset in CONNECT not the workspace.

    The CONNECT products as Jan mentions needs a Workspace/Workset - there is not really a way around it.

    What I have done with my configuration is since all projects for a specific client will not change (they are always the same set of configurations) is set the workspace up as merely a figurehead. There is no real configurations for this, other than to point to the workset. In the workset is where I put all the configurations. I have a workspace with the client name and then a workset with the client name.It seems like a waste setting the workspace and workset to the same name, but really only the workset contains the needed configurations. So instead of setting up the workspace with the clients resources (as you have done), set up the workset with them and just use the workspace to point to the workset.

    Timothy Hickman

    CADD Manager | CADD Department

    timothy.hickman@colliersengineering.com

    Main: 877 627 3772| 

    1000 Waterview Drive Suite 201 | Hamilton, New Jersey 08691

    Answer Verified By: Robert Schwenn 

Reply
  • And from my point of view our old project level now should be "Workspace" level, because it contains client resources. It seems that Bentley agrees here.

    This is not a correct statement. The project in V8i would be your workset in CONNECT not the workspace.

    The CONNECT products as Jan mentions needs a Workspace/Workset - there is not really a way around it.

    What I have done with my configuration is since all projects for a specific client will not change (they are always the same set of configurations) is set the workspace up as merely a figurehead. There is no real configurations for this, other than to point to the workset. In the workset is where I put all the configurations. I have a workspace with the client name and then a workset with the client name.It seems like a waste setting the workspace and workset to the same name, but really only the workset contains the needed configurations. So instead of setting up the workspace with the clients resources (as you have done), set up the workset with them and just use the workspace to point to the workset.

    Timothy Hickman

    CADD Manager | CADD Department

    timothy.hickman@colliersengineering.com

    Main: 877 627 3772| 

    1000 Waterview Drive Suite 201 | Hamilton, New Jersey 08691

    Answer Verified By: Robert Schwenn 

Children