in our organization we work in a workspace/workset configuration within our cad operators have to load/open different dgn files not assigned to any worksets.
Is there an environment variable/method/function im CONNECT to suppress the workset verification? Because the dgn files were manipulated from different worksets. An assignment to only one workset isn't practical.
I moved the dgn files to directories the variables MS_WORKSETMISMATCH_ALERT_EXCLUDE_* are pointing to but at all times the workset alert message appers.
the dgn files are within a folder reached by MS_SEEDFILES. My last attempt was open the files from _USTN_WORKSPACESTANDARDS)seed\.
This will need some more investigation.
I can reproduce the behaviour with a dgnlib from one of my workspaces that should be omitted from the mismatch check by both variables.
are there any news in this topic?
Agree this has been around for too long.Trying to run scripts through 1000's of files is just unworkable without being able to disable this simply.MS_WORKSETMISMATCH_ALERT_EXCLUDE_VARS_ALLLEVELSMS_WORKSETMISMATCH_ALERT_EXCLUDE_VARS_WORKSPACELEVELset to C:\Temp\ or _DGNDIRdont seem to remove the issue.a real problem. all our data is in PW and we have to pull it out do run audits and updates having to click the workset button for every file is not the answer
We added a new variable in Update 14 that will supress the whole WorkSet branding behaviour:
MS_SUPPRESS_FILE_WORKSET_ASSOCIATION = 1
Please give this a try and let us know if it does what you need.
Hi Marc,It doesnt work.Still throws the dialog.Unable to process files in bulk using connect its a real problem.I added the variable (its in my ucf) as shown aboveUstn versions 10.14.02.01
the variable works as designed i believe. it suppresses the workset association, not assign one. so when in use it actually uses the no workset choice. i would like to see a variable that would suppress the question of changing the workset and just use the workset that is selected in the open dialog.
Applying the variable doesnt stop it throwing the dialog on every file open, this is what it should be stopping its not what i would say is WAD.You cant run a script through 1000's of files and have to click a button for each file that doesnt make sense.
The WAD is what it is doing is what i am saying. it was not designed to suppress the notification, it was designed to suppress the workset association therefore it associates no workset when file is opened. it appears you want to reassign a workset, whether it be No Workset or whatever, but i can see where that is not this variables purpose.
As i stated above, i would like a variable to suppress the notice of different workset and just use the currently selected one to open file. it is up to the user/designer to select the correct workset to be in, therefore it should open the file and not enquire about previously assigned workset or tell you that it is different than what was branded on it before. reassign it and move on, nothing to see here.....