Hello everybody,
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.
best regards
Daniel
Hi Marc,
the dgn files are within a folder reached by MS_SEEDFILES. My last attempt was open the files from _USTN_WORKSPACESTANDARDS)seed\.
Regards
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.
Marc
I think we both want the same thing.I want to suppress anything to do with the workset. not change or reassign just ignore it.as i run scripts all the time.
We are currently using ProStructures Update 5 and this variable does not seem to work for this product. Will it be common across all products soon?
It works in MicroStation Connect Update 15.
Hi Marc, is there any update on this?
It seems to either need more explanation or something around how its implemented as its just not working as we are expected.We all want the dialogs to be ignored I need a way to batch process files outside of a PW environment on an automation server.
@Dan.Eng@bentley.com
can you look at this please
@Ben - it looks like it suppresses anything going forward. It and it appears like you already have DGNs associated to a workspace/workset.
So no - this variable is NOT what you want.
Bentley STILL needs to come up with what you are asking for.
I believe there are several options that could be considered:
1. Keep as is and get the message.
2. Suppress the message and leave the current workspace/workset.
3. Suppress the message and change the workspace/workset to what was assigned to the DGN.
Timothy Hickman
CADD Manager | CADD Department
timothy.hickman@colliersengineering.com
Main: 877 627 3772|
1000 Waterview Drive Suite 201 | Hamilton, New Jersey 08691
We still need a solution for the USE case we have.I think there needs to be a switch and as you say that could have multiple options.At the moment all i care about is canning the message dialog so scripts can run enmasse without having to accept each file.But if thats getting sorted they the options you describe work for me.maybe add one more4. Suppress the message and change the workset to the current workspace/workset
@Ben Davis: I agree with you in all topics! We need a 'switch' like a variable that disables the workset-mismatch alert. Branding is OK. If we run vba scripts on 1500 dgn files, I would never clicking away the workset warnings.
This is precisely what we requested, and were promised MS U15 would provide: 1-As-is, 2-Use Active WorkSet, and 3-Use DGN's WorkSet.
It appears they may have decided to give us only Option 3, which does us little good as the only option. We may have been waiting for MS U15 in vain.
Hi Houck,
If you've filed a service request or got an ER number for this issue, would be great if you can share it.
We cant keep the messagemy use case is this.Data and workspace reside in Projectwise (not always ours) different projects too.Files pulled from PW and run through scripts - many many many reasons 1000's of files and oftenDialog prevents script from running (have to acknowledge dialog each file)= automation is not available without significant effort recreating workspaces that arent ours = significant additional costs
We just need a variable to ignore the dialogWe have had no movement or time frame on this its impacting large massive scale projectsPhil Conard is this something you can expedite please?