Where can we get an update on a defect dealing with dgnws files and their locations?

This Defect currently remains open and is linked to your Service Request 7001069899.

If you would like further assistance or need an update on this then please enquire via your Service Request.

Any resolution to this defect?

We would like to maintain the integrity of our CFG files by prohibiting users from potentially editing them, but would love to use the functionality of the DGNWS provides.

Hi Charles,

That specific defect has not progressed, however other defects relating to DGNWS have been fixed which may affect your situation. 

One approach that I have taken in a (deliberately) simple example configuration is to define a custom variable setting the location for my project data folders in WorkSpaceSetup.cfg :

SMB_PROJECTS = D:/_SMB/SMB_Projects/

then set the appropriate variables in the WorkSpace.cfg file as follows:

_USTN_WORKSETROOT = $(SMB_PROJECTS)$(_USTN_WORKSPACENAME)/$(_USTN_WORKSETNAME)/

_USTN_WORKSETDGNS = $(_USTN_WORKSETROOT)dgn

_USTN_WORKSETDGNWS = $(_USTN_WORKSETROOT)Standards/$(_USTN_WORKSETNAME).DGNWS

This results in the DGNWS being stored in the WorkSet Standards folder. This is a test example on my local D:\ drive inside the _SMB folder, but SMB_Projects and SMD_Resources could easily be located on separate mapped drives with admin/user permissions set appropriately.

The SMB_PROJECTS custom variable is convenient for my case but could be replaced by hardcoded paths in the WorkSpace CFG files. This is in MicroStation but the principles should apply to OpenRoads.

Marc-Thank you for the reply.

Ironically, I kind of have a similar setup.  I have my corporate and client workspaces on a separate drive from our production DGN files.  I have a custom variable Client Projects that defines where the project DGN files are located

Client_Project      = X:/<CLIENT NAME>/<CONTRACT NUMBER>/
_USTN_WORKSETROOT          = $(Client_Project)$(_USTN_WORKSETNAME)/
_USTN_WORKSETDGNS          = $(_USTN_WORKSETROOT)02 Draw/
_USTN_WORKSETSTANDARDS     = $(_USTN_WORKSETDGNS)05 Application/
_USTN_WORKSETSDGNWSROOT    = $(_USTN_WORKSETSTANDARDS)
_USTN_WORKSETDGNWS         = $(_USTN_WORKSETSDGNWSROOT)$(_USTN_WORKSETNAME).DGNWS

the above being defined in my workset.cfg file since the acual location of the project DGN's are located in a specific subfolder within a standard project folder setup.

All of the config files exist on another drive, the DGNWS file is the only config file I have "with" the project.

I should also mentioned that I added a TON of custom properties in my standard workset.  I was under the assumption that it gets added to that DGNWS file.. so I made it my DGNWS template... and of course NONE of the custom properties went with...

BUT.. as long as my DGNWS file exists in the same folder as my workset cfg… all is good.

Submitted a support request, received a response that its a logged defect (defect 1116741), supposed to be resolved in update 17.

So...next year...

at this rate... if we're lucky

at this rate... if we're lucky