MicroStation Connect Update 13
I am trying to control the version of the .imodel version being published with a script to 1.6 and not 2.0. It looks like the settings file I created and that is loaded is not supporting the imodel version output setting. Anyone have any ideas or solution for this issue before I file a ticket?
Mark Winegar said:I am trying to control the version of the .imodel version being published
What happens if you execute key-in PUBLISHDGN CREATEDGNDBIMODEL?
Regards, Jon Summers LA Solutions
it publishes to the latest version, 2.0. No way to control the version setting via keyin or settings file, at least nothing in the settings file that represents that the version is set to a certain version. So far I am unable to control the dialog through vba either.
Junaid Khan said:We could add this option by default with MSTN key-ins
Either that, or clarify MicroStation Help to include those *.exe options.
Junaid Khan said:If you browse to the ITG directory C:\Program Files\Bentley\ItgDgnDbImporter 1.5\ you will find the Bentley_DgnDb_iModel_Importer_2.0.pdf ReadMe for similar details
If your job involves working with the ITG directory, then I'm sure that's a good place to look. But, for the average MicroStation user, is it reasonable to expect him to make that unintuitive exploration? MicroStation Help is a well-known document, available from the MicroStation UI. If you want to make a user aware of arcane key-ins, put them in MicroStation Help. If you want to make a user aware of a well-hidden PDF document, put that in MicroStation Help as well.
The PDF documents you cite have the title Bentley DgnDb iModel Importer. That's misleading to a MicroStation user, who wants to publish or export DGN data. They don't want to import an iModel: they want to export an iModel.
If you browse to the ITG directory C:\Program Files\Bentley\ItgDgnDbImporter 1.5\ you will find the Bentley_DgnDb_iModel_Importer_2.0.pdf ReadMe for similar details. Hope that helps. Thanks
defect has been filed against this issue in MicroStation.Defect Report 799669.
Now to focus more on the imodel importer. I have the help doc but having issues getting it to successfully pull, publish and push back into ProjectWise. Filing a ticket for more assistance since the script does not provide any feedback on error handling or success.
Thanks for info. If I could control anything since the settings file is not honoring the .imodel version, vba would be my next goto since my process is completely written in vba with calls to keyins but my understanding/research is showing me that I have no way to send the command into the publish app and control it. I do not use the SDK so I do not have access to call the api for the importer without getting a coder which in the long run may be what happens. Not sure yet. In the meantime I am playing with the importer via the command line but am unsuccessful in reaching into ProjectWise successfully. I am not getting errors but it is also not publishing anything. I will be filing a ticket on this task for more help.
With that said, I ended up filing a ticket since this subject is a hot item on our end due to our PW Automation process is failing. In short, I have written some vba being executed via the ProjectWise command console but the version issue control is missing. A MicroStation defect was filed today on this regarding this. Defect Report 799669.
I am having problems getting the console to actually work in ProjectWise. I can get it to run locally but nothing in ProjectWise. The documentation helps with the switches but no examples are provided for either the local or a ProjectWise workflow.
If you want to publish the .imodel from an i.dgn in MicroStation CONNECT in ProjectWise, open key-in dialog and execute key-in publishdgn createdgndbimodel <path of .imodel> <path of .i.dgn>, please use quotes to overcome any spaces. I have also asked development for achieving similar directly from the ITG console.