[CE] Open file to selected workset

The default behaviour of the WorkSet association feature is that a file is "branded" with the WorkSet it is created in, e.g. WW1.

If that file is opened in WW2 it will prompt the user to decide whether to continue to open the file in WW2 and associate the file with WW1", or to change the active WorkSet to WW1 to follow the existing file association.

My current understanding is that MS_SUPPRESS_FILE_WORKSET_ASSOCIATION = 1 supresses the dialogs but does not affect any existing association, so it seems that in your case the associated WorkSet is being loaded. This is a recently added variable so I have not yet tested that scenario myself. Further development work is in progress on the behaviour of this variable.

If you wish to completely disable WorkSet association two key-in commands can be applied to a file:

FILE DISASSOCIATEWORKSET followed by FILEDESIGN SAVE SETTINGS (necessary to save the change in association status)

as discussed in Help > Home > Getting Started > Fundamentals > Working with DGN Files > Including Files in the Active WorkSet

I don't mind dgn being branded to the active workset. The issue I have is if a user selects WW2, with MS_SUPPRESS_FILE_WORKSET_ASSOCIATION = 1, and accidentally open a WW1 branded dgn, they might not realise they've been working in WW1 configuration until too late. 

I made a post in the ideas section - to change the branding.

Move it from being on the file, to it being on the folder that the file exists in. 

If it works with the folder being the determining factor for the configuration then moving or copying files would not have any issues.

Also non preferred Tim. How would that work if there're multiple dgn folders associated with a workset? Again, depends on the way folder branding is implemented, it might break something else.

Currently we have a controlled way for users to select the workset (including preventing them from selecting worksets that they aren't assigned to), if that can be bypassed just because of opening a dgn, then that control is pretty much useless. 

An example of how we mitigate dgn opened in wrong workset. Normally, our dgn will reference the master layout cuts sitting in another dgn. And reference paths are explicitly defined at workset level.

If a dgn is opened in the wrong workset, user won't see any reference coming through and knows something is wrong somewhere. If now a workset is activated "behind the scene", we lose that mechanism to tell the user they are in the wrong workset. I can set the title bar to show the active workset name, but that doesn't stop people go ahead and work in a dgn they are not supposed to work in. 

well - you said it.

It depends how the branding is implemented.

that's the thing, a new feature as drastic as branding should have a way to be turned off, shouldn't be rolled out as "take it or leave it". 

that's the thing, a new feature as drastic as branding should have a way to be turned off, shouldn't be rolled out as "take it or leave it".