If I set the _USTN_WORKSETDGNWSTEMPLATE variable in a workspace config file, the msconfig.cfg is being looked at again (Specifically on line 471) and overwriting what I set at the workspace level. In doing so there is no way I can see to point to an alternative DGNWS file name for different workspaces.
I set it at the organization level and then lock it. I've tested it at the workspace level (still locking it) and that also worked.
Answer Verified By: Ryan Mann
Thanks Kevin that's what I needed.
Hi Ryan, please let us know if this adds any useful info for you: CONNECT Edition - Configuration Tips : Where should I keep my DGNWS files?
Marc
No Marc. That info doesn't really pertain to what I was wanting to do.
OK, thinking back I now recall trying DGNWS variables in a WorkSpace config and it not working. Locating them there was not critical to the examples that I was working on and I arrived at the WorkSpaceSetup.cfg as the best place to locate them without resorting to locking the variables (in my context at least). Typically:
# locate DGNWS in WorkSet Standards folder_USTN_WORKSETSDGNWSROOT = $(_USTN_WORKSETROOT)Standards/_USTN_WORKSETDGNWS = $(_USTN_WORKSETSDGNWSROOT)$(_USTN_WORKSETNAME).DGNWS
Using _USTN_WORKSETSDGNWSROOT gave the most reliable results. For more complex scenarios %if logic can be used in WorkSpaceSetup.cfg.