I have an annoying situation where I am attempting to call MicroStation OpenRoads Connect series with a command line to process files using a keyin file.
I specify the command line in the format.
"C:\.....\OpenRoadsDesigner.exe" "-WKMyWorkspace" "-WWMyWorkSet" -O "-SC:\Temp\keyins.txt" "C:\DGN\MyFile.dgn"
I wish to open the file in the specified workspace and workset but if the file was used in a different workset it pops up the "WorkSet Not found Alert" dialog and stops all processing waiting for user input. It does not run the commands.
Is there a way to force MicroStation to open it in the specified workset and thus avoid the dialog pausing the process?
Thanks.
My first comment would be to remove the double quotes - for example, "C:\.....\OpenRoadsDesigner.exe" -WKMyWorkspace -WWMyWorkSet (you only need the quotes around WorkSpace and WorkSet IF they contain a space).
I have only used made up names in the example. The actual names may have spaces in the future. In any case even though they are superfluous if there are no spaces in my experience this will not have any bearing the parsing of the arguments.
I do not think it is possible to force the file to open in a different workset, as the DGN is 'branded' with the WorkSpace/WorkSet combination. I tried renaming the original WorkSet cfg and dgnws files, to see that would help - it did not as you still get a dialog saying that the WorkSet could not be found.
Thanks anyway. Maybe a CR could be useful. Being able to command line process this way is a quick way to automate things for basic users but if the process comes across an odd file like this case it will pause.
I will build an INITAPPS app next and see how that goes.
Hi Stirling,
Stirling Hamersley said:Is there a way to force MicroStation to open it in the specified workset and thus avoid the dialog pausing the process?
I have no hands-on experience with this issue, but you can try to play with configuration variables settings.
I recommend to check MS_WORKSETMISMATCH_ALERT_EXCLUDE_VARS_ALLLEVELS and MS_WORKSETMISMATCH_ALERT_EXCLUDE_VARS_WORKSPACELEVEL, from the description it seems using these variables it's possible to define what files will be not checked for correct Workspace/Workset configuration.
With regards,
Jan
Bentley Accredited Developer: iTwin Platform - AssociateLabyrinth Technology | dev.notes() | cad.point