been messing around with this for a while now and just cant seem to find good information on this.
I set up a sheet index with default folders. I now want to use this as the template dgnws file so if one ever gets deleted for a workset this one will be used so the default folders are there.
so it works fine when creating a new workset as I just select the template workset like this...
when I open a file and look at the sheet index I have the folders I expect..all is good.
but now lets saw for some reason that dgnws file gets deleted. the next time I open microstation the dgnws gets re-created. but now it looks like this...
which is not right. the TEST_WORKSET line in the image above is blank and the 000000_OHDOT_Template one has all the default folders.
So my question is I must have something wrong in the configuration but when looking at all the variables I'm a little bit confused what needs to be set..here is what I have set..
_USTN_WORKSETDGNWSTEMPLATE I have this set to the 000000_OHDOT_TEMPLATE.dgnws file in my cadd standards at the workspace level
_USTN_TEMPLATEWORKSETNAME I have this set to the value 000000_OHDOT_TEMPLATE. (I also tried it with this undefined and got the same results)
I see things like _USTN_WORKSETDGNWSROOT (which is undefined for me) and USTN_WORKSETTEMPLATE that points to some WorkSet.Template file (not sure what that's used for)
but nothing is really jumping out at me. any one else running into this problem or have any suggestions.
I have an SR and Defect on this issue.
~HTH
John.
yep
okay thanks.. i see the post on the administration forum now..but this causes a problem is your using projectwise as you cant create the workset from the microstation dialog. so when projectwisethe _USTN_WORKSETDGNWSTEMPLATE is pretty much the only way to get your dgnws file created for the workset.
John Drsek said: this causes a problem is your using projectwise
Aha! So ProjectWise moves into the frame...
Regards, Jon Summers LA Solutions
Its just buggy, if it's fixed and works as defined then it will work in PW too. You may want to contact Bentley and add to the Defect.
John
With PW, do you know if you are using a managed Workspace or not. This can have a massive effect on what is loaded..... and from where, plus how it is controlled ie permissions
if you open the Workspace Configuration in MS from a DGN opened in PW... look at the DGNWS var and see where it is pointing to and then check the path exists inside the PW environment
Ian .
yes its a managed workspace. the variables are fine and defined correctly. the same thing happens inside and outside of projectwise (the defect is really on microstation and not projectwise). but projectwise doesnt really give you a way to create a workset, even though you can have a managed workspace..felt like this piece was just kipped over.
basically in projectwise you create a projectwise Project. which in my case is the same as a microstation workset folder. but then you need to create the workset.cfg file (just copy from the a template cfg). but then you let the dgnws file get created once someone goes to open that workset in microstation. it creates it but its the same problem as if you delete the dgnws file outside of projectwise when it gets recreates it has two item sheet indexes, the open print organizer button doesnt work, basically the whole sheet index tab is messed up. Also the permissions are taken care of already, ie anyone working with microstation needs access to this dgnws file.
SO in short to use worksets in projectwise across your offices you will pretty much need some custom programming as you cant expect the end users to create the folder then create the cfg file..soo for us internally were developing a little app to handle this shortcoming. BUT in my opinion if projectwise is going to suppose a managed workspace then it should also be able to create a workset out of the box.
i will follow up with Bentley on this defect, but as of right now there is no other way to get this to work short of not defining any default stuff in the sheet index.
thanks everyone