I have read the Wiki on "How to create additional WorkSet properties for use as Text Fields".
My Workset is already created so I am trying to add a new custom property to the Workset from the right hand side of the Work Page area. (Not from the Workset drop down)I click on the Properties drop down and select Advanced Properties. From the Edit Workset dialog that pops up, I select Add a Custom Property. I choose Text Propertyand then fill-in a value. (In this case I just used Test1). I also filled in the Description section. Everything appears correct right before I open the file.
I open a MicroSation Connect file, Save the file, and then exit. When I re-open the Work Page area, the WorkSet properties that I just created are gone. They have been wiped out along with the Description section.What would make the dgnws file clear itself?
I have set the following variables in the WorkSpaceSetup.cfg. #### Set Variable for Workset DGNWS directory _USTN_WORKSETSDGNWSROOT = $(MS_DEF)
#### Set Variable for Workset DGNWS file name _USTN_WORKSETDGNWS = $(_USTN_WORKSETSDGNWSROOT)$(_USTN_WORKSETNAME).dgnws
Note that the MS_DEF location (I Drive) is different than the Workspace (N Drive). The dgnws file is located on the "I drive" with the workset dgn files. Using MicroStation Connect version 10.12.00.400 update 12
I'm still testing this issue. I think my problem is where I'm defining my variables. The hierarchy of the location for the worksetsdgnwsroot is probably causing the problem. I've tried defining it in the workspace cfg, and the workset cfg. Ultimately the worksetsdgnwsroot was utilizing MS_DEF which was defined in the Workset cfg.
My company doesn't want the users to have the security ability to change the configurations on the "N drive". They can only read from it. That's why all the project files are located on the "I drive" where they have full rights. This is where I'm attempting to place the dgnws file.
We do something similar. Here is a test WorkSet CFG that puts the DGNws file into the WorkSet root folder. There are some bugs so becarefull. First one you find is that by default it creates the DGNws in the WorkSets root folder, delete it and it will recreate in the correct location.delme123.cfg
~HTH
John.
yep
I took your advice and it worked. I used a variation of your method but the concept is the same.
1.) I made a single directory dedicated purely for the DGNWS files. (This directory has rights for all users).
2.) I placed my dgnws variables at a higher level. I put them in my Organization cfg file. What I call the old Site file.
John, instead of deleting the initial DGNWS file, I found that I just have to open MS Connect twice. I can populate the Property fields of the Work Page anytime after the second generation.
I believe this whole issue to be a bug that needs fixed by Bentley. They assume that the Workset will be a subdirectory of the Workspace. That is not the case for our company setup. The DGNWS file should perform the same no matter how or where the location is defined.
Karl Todt said:instead of deleting the initial DGNWS file, I found that I just have to open MS Connect twice.
I would still delete the first one it creates, just to avoid confusion.I agree, I have several defects on the WorkSet stuff. They have informed us they will be addressed in mstnCEr13
Karl Todt said:I believe this whole issue to be a bug that needs fixed by Bentley. They assume that the Workset will be a subdirectory of the Workspace. That is not the case for our company setup. The DGNWS file should perform the same no matter how or where the location is defined.