We were wondering what kind of progress has been made on providing options for the WorkSet Mismatch issue, and what sort of solution Bentley is pursuing?
We do *not* want the WorkSet Mismatch notification simply turned off. We typically want the currently Active WorkSet to be used for any DGN file that a user opens up, or at least have that option.
When Bentley was originally describing their ‘fix’ to this issue, they proposed setting it so the DGN file’s branded WorkSet (if any) was going to be the default; this is the opposite of what we usually want/need.
I amended our Service Request to Bentley to stipulate that we would like to have the following options:
1-leave it as is (notify of WorkSet mismatch)
2-use currently Active WorkSet
3-use the DGN file’s currently branded WorkSet.
We have over 20 WorkSets, and DGN files could be worked on by several overlapping WorkSet users, so if someone wants to batch Plot, or other operation, they want to use their currently Active WorkSet, and not be notified about a mismatch. Other times, they may want the notification. However, we definitely do not want to always use whatever WorkSet the DGN file is already branded with.
Are the above options being considered as a solution to the WorkSet Mismatch notification issue?
TIA,
G.Houck
Hi Geoff,
The notes I have seen say that a variable has been added, the effect of enabling this variable should be that files will be opened using the active WorkSet disregarding any branding form other WorkSets, option 2 above.
Options 1 and 3 above are current behaviours.
I have not tested this myself yet, but it is showing as tested in the enhancement.
Marc
I am using Update 16 & I still cannot find any reference to this variable.
Are you able to follow-up with its syntax (if it has been implemented)?
Hi John,
The variable is MS_SUPPRESS_FILE_WORKSET_ASSOCIATION.
I am advised that if this variable is set to true, i.e. '1', the file which user is trying to open will always open in its associated WorkSet, which is option 3 from Geoff's list in the original post.
I have not tested this thoroughly yet but you should find it behaving as described.
This variable is not defined by default, but can be added at the appropriate level in your configuration:
MS_SUPPRESS_FILE_WORKSET_ASSOCIATION = 1