When opening .dgnlib files to edit levels, text styles, or whatever, I am often confronted with the WorkSet Alert dialog.
Since dgnlibs will be used by multiple WorkSets I usually like to have mine not branded - No WorkSet. Sometimes, however, I'll be in a hurry and just click the Open button on the alert dialog, and brand the dgnlib to my active WorkSet. So far I have not encountered any adverse effects of branding vs. not branding dgnlibs.
Is there anything good or bad about branding your dgnlibs, not branding your dgnlib to a WorkSpace, or doesn't make any difference?
Hi Zane, please can you send us links to the source of this comment so we can understand the background and perhaps contribute to that discussion?
Zane Pratt said:From what I have read this screws up your managed workspace in Projectwise.
I don't think that branding affects ProjectWise, but am checking to be sure.
Marc
FYI
https://communities.bentley.com/products/road___site_design/w/road_and_site_design__wiki/37999/how-to-disassociate-remove-a-workset-from-a-dgn-to-be-able-to-load-a-projectwise-workspace
Branding files is very confusing to users. Especially to users managing dgnlibs. In v8 you could open dgnlibs under a workspace, Now the file is branded to a workset (project). How does this effect Microstation, if we want to use a dgnlib for multiple worksets (projects) and it is branded to a single workset (project)?
David Trejo-Rodriguez said:i can file an enhancement to suppress the alert dialog if the file is a dgnlib is this would find that helpful.
That's the answer, but will Bentley actually do that? [a workaround]You could just close your file first, then select No Workspace. After you open a few libs they're show up on the MRU list.
Connect r17 10.17.2.61 self-employed-Unpaid Beta tester for Bentley
Hi Zane,
Thanks for that link. I'll flag that with the product managers. Branding and it's implications are being discussed.
Marc Thomas said:I'll flag that with the product managers. Branding and it's implications are being discussed.
That's great, thanks!
It would be nice (in fact, I think it's crucial for migration to CE and its smooth implementation) to have exact description how to work with dgnlibs.
It seems when Bentley designed workspace/workset structure and branding all files, this issue was missed. When there is e.g. dgnlib on workspace level (not specific for particular workset), what is correct way how to work with it (because every file is automatically assinged to workset also)? How to work with organization-wide dgnlibs?
It's Bentley responsibility to provide these best practices ... and I understand that many CAD administrators are confused / angry / annoyed by CONNECT Edition platform when they are required to spend huge amount of time to investigate what works the best, but without any confirmation it's really the best way.
With regards,
Jan
Bentley Accredited Developer: iTwin Platform - AssociateLabyrinth Technology | dev.notes() | cad.point