GUI DGNLIB is not editable on the Network

Do you also have the network location as part of the MS_GUIDGNLISTLIST ?

Yes,  If I didn't I wouldn't even be seeing the customization...

Ugghhh..,  SERIOUSLY??  I just changed all network paths to UNC per request from our I.T. department for the release of Connect.  I had never thought of that.  Thanks for the insight...  Is anyone from Bentley on board to respond??    I will try testing this and if it does work with drive letters I will file as a defect...

Thanks Bruce!

Random question...

Do you have read-write access to the network DGNLIB folder? I would assume you do, but stranger things have happened.

yes.  I do have access.  I'm thinking Bruce may have it.  I have not tested changing to drive letters yet but its on my list of things to try.

Ok.  So I verified this is because of the UNC path.  I will file a defect report.  Thanks all!!!

For the verification purpose, I could not reproduce it from my end. Here enclosed four images (for both network drive and unc path) telling the modification is available at after opening the target file from Customize > File > the dgnlib file.

For the verification purpose, I could not reproduce it from my end. Here enclosed four images (for both network drive and unc path) telling the modification is available at after opening the target file from Customize > File > the dgnlib file.

Your third image using the UNC path to the Bentley file service is not Editable.  Notice the UM-Menu items are all grayed out.  You can not select them or edit them.  You have just reproduced the issue.

The first and third images are definitely not modifiable because the target file was not opened yet. So, the expected results can be found at both second and fourth images.

Hyung

Hyung,

I'm still not sure we are understanding each other.  If you put the um-menu.dgnlib or personal.dgnlib on a network drive mapped to a drive letter and open it from that location with _USTN_CUSTOM_CONFIGURATION pointing to a UNC path the ribbon menu will be gray and not editable.  It should be editable from the network.  When I change my variables (_USTN_CUSTOM_CONFIGURATION ) to point to a drive letter it will open and be editable.  

It's not just where the files reside (I have them on my computer on a mapped network drive) but I'm setting the variable to locate them to the unc path. In this setup you can not edit the dgnlib... 

In our organization different groups may map the file location to different drive letters thus why we want to use UNC path to access Microstation in our installations.

_USTN_CUSTOM_CONFIGURATION=\\\ae-it-fileprod1\AE-ProgramFiles\CAD\Bentley\UMConnectConfiguration\

Complete file (ConfigurationSetup.cfg)

[General]
_USTN_CUSTOM_CONFIGURATION=\\\ae-it-fileprod1\AE-ProgramFiles\CAD\Bentley\UMConnectConfiguration\

[SetConfiguration]
%if !defined (_USTN_USER_CONFIGURATION)
%if defined (_USTN_CUSTOM_CONFIGURATION) && ($(_USTN_CUSTOM_CONFIGURATION) != "") && exists ($(_USTN_CUSTOM_CONFIGURATION))
_USTN_CONFIGURATION = //ae-it-fileprod1/AE-ProgramFiles/CAD/Bentley/UMConnectConfiguration/
%endif
%endif

Mark,

Was the cfg file generated by the installer? Or you modified the file? I am curious why you have triple backslash at the beginning of the first path. The installer would not recognize the path if you used Custom Configuration field. I suggest you to uninstall the product and restart the installer using the valid unc path (e.g. use double backslash) which will convert to valid forward slashes in the cfg. Once the installation is complete, select your workspace menu under Custom Configuration in WorkSet screen. Then, open your dgnlib file. Here enclosed an image for reference.

Hyung