ProjectWise Managed Workspace Will NOT Pass WorkSpace Name to ORD

RE: ProjectWise Managed Workspace Will NOT Pass WorkSpace Name to ORD

Kevin van Haaren — Thu, 23 Jun 2022 12:58:06 GMT

[quote userid="468719" url="~/products/projectwise/f/projectwise-di-forum/231655/projectwise-managed-workspace-will-not-pass-workspace-name-to-ord/718178"]I joked to my wife that you live in these forums because when I go hunting through them you respond to almost all the threads that come up for me[/quote]

urk. i have an rss feeds of a couple of forums and i'm a slave to my rss feed rearder :(

If i see one i can answer quickly i usually will. my first response was from my ipad and from memory. Longer response below is a modification of my notes on workspaces.

RE: ProjectWise Managed Workspace Will NOT Pass WorkSpace Name to ORD

Kevin van Haaren — Thu, 23 Jun 2022 12:24:32 GMT

Great. I think this was one of the things that threw me when i first started working on moving an ORD workspace into ProjectWise (actually I think this is more how ORD workspaces in general work as well). I just wanted to test up to the WorkSpace level so didn't set anything workset stuff. Took me a while to figure out you have to set a workset too or ORD won't accept the workspace name.

Here's the basic outline that I use, it might help going forward (or anyone else stumbling on this):

Predefined CSB => Define _USTN_CONFIGURATION, point to a projectwise folder
    ORD autoloads WorkSpaceSetup.cfg from this location
        WorkSpaceSetup.cfg defines:
            _USTN_ORGANIZATION
            _USTN_WORKSPACESROOT (workspaces with an s)
            _USTN_WORKSPACEROOT  (workspace no s, this path includes the workspace
                name, but the name isn't defined yet)
        	_USTN_WORKSPACESTANDARDS
        	_USTN_WORKSETSROOT (worksets with an s)
        	_USTN_WORKSETROOT (workset, no s. this path includes the
        	    workset name, which isn't defined yet)
    ORD autoloads *.cfg from _USTN_ORGANIZATION folder
        I have our corporate standards here
WorkSpace CSB => Define _USTN_WORKSPACENAME
    ORD autoloads workspacename.cfg from _USTN_WORKSPACESROOT
    Also *.cfg will be loaded from _USTN_WORSPACESTANDARDS folder
WorkSet CSB => Define _USTN_WORKSETNAME
    ORD autoloads the worksetname.cfg from _USTN_WORKSETSROOT folder
    *.cfg is loaded from _USTN_WORKSETSTANDARDS folder

I lock all the _USTN variables I set in that list. When I say a cfg file is autoloaded I mean a literal .cfg file in ProjectWise. I don't do any %includes to manually include cfg files. I put all other variables in one of the cfg files that are in projectwise. I try to avoid doing anything else in CSBs.

One other trick I have is I define a root variable in the Predefined CSB. This is 1 of two places I set a ProjectWise folder in a CSB. All my other variables are strings referencing that variable. The other location is I set _USTN_WORKSPACESTANDARDS based on DMS_PROJECT(_DGNDIR) and _USTN_WORKSETNAME to lastdirpiece(DMS_PROJECT(_DGNDIR)). This way I don't need a custom workset CSB for every project.

This differs from the Dynamic Config, but I believe it uses the same basic principles of defining the bare minimum in CSB and letting ORD auto-load cfg files from paths it defines. (I also don't try and do a single config for both V8i and ORD)

RE: ProjectWise Managed Workspace Will NOT Pass WorkSpace Name to ORD

Christopher Williams — Thu, 23 Jun 2022 05:36:25 GMT

Kevin,

I was having dinner with my family when your response came in and I was keeping an eye on my phone hoping someone would respond. I joked to my wife that you live in these forums because when I go hunting through them you respond to almost all the threads that come up for me. Bentley should be paying you a consulting fee.

The variables were all locked, but Bentley's Dynamic Managed Workspace cfg files never defined any of the _USTN_WORSET* variables. They defined their _DYNAMIC_WORKAREA stuff but then never set it to the _USTN version. As soon as I did that everything came in.

I still have some finessing to do on TxDOT's standard Workset.cfg file, but everything is finally loading up.

Thank you so much!
Chris

RE: ProjectWise Managed Workspace Will NOT Pass WorkSpace Name to ORD

Hinesh Mistry — Thu, 23 Jun 2022 02:50:13 GMT

Hi Chris,

Please feel free to reach out to me and we can certainly help. My email is hinesh.mistry@pencil9.com or use my meeting booking link: https://calendly.com/pencil9-hinesh/30min

Kind regards

Hinesh

RE: ProjectWise Managed Workspace Will NOT Pass WorkSpace Name to ORD

Kevin van Haaren — Thu, 23 Jun 2022 01:51:48 GMT

Are you also setting a workset name?

have you tried locking the workspace name variable (and workset name)?

do you have a .cfg named for the workspace name in the folder pointed at by workspaces root variable? Same for a workset name .cfg in the worksets root folder.