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.
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.
The Bentley DgnDb iModel Importer converts DGN V8-format packaged i-models (.i.dgn) into the compressed DgnDb-format or BIM-format (.imodel) iModels. So in technical terms it imports all the contents of the DGN into a fresh .imodel (Sqlite DgnDb file), hence this naming convention was used. Also in the Publish i-model(s) Dialog Help chapter, there is a tip referring to same .pdf file. The location of the .pdf was removed because there were three version of DgnDb Importers and mentioning different versions simultaneously were not possible. Tip: To learn more about creating .imodels using the Bentley DgnDb iModel Importer or other supported file-formats conversions in batch mode, refer to the help in .pdf file available in its installation directory.
Junaid Khan said:in technical terms it imports all the contents of the DGN into a fresh .imodel
I'm sure, technically speaking, that you're correct. However, help manuals should reflect the product user's viewpoint, not that of the author of the tool.
Junaid Khan said:To learn more about creating .imodels using the Bentley DgnDb iModel Importer ... refer to the help in .pdf file available in its installation directory
The DgnDb iModel Importer is mentioned in MicroStation help. However, there's no mention that DgnDb iModel Importer is a separate executable, there's no mention of that PDF help document, and there's no mention of a separate installation directory. Why can't the useful information you've written above be added to MicroStation help?
do you have more information on how the nomenclature of logging into a ProjectWise Datasource and pulling/pushing the data should be? The documentation you are referring to provides no examples and I am unable to get past this roadblock. I can generate the DBimodel with no issue when outside of the ProjectWise environment.
I need to know:
An example provided with this tool in the documentation would be a huge plus for both in and out of the ProjectWise environment.
I have placed a ticket on this Friday, Oct 18th but no response at this time.
Hi Mark, i am still waiting for more updates from Dev team, but have you tried the key-in publishdgn createdgndbimodel <path of .imodel> <path of .i.dgn> in ProjectWise. If you don't need the .imodel 2.0 format you can temporarily uninstall it and then this key-in will generate the 1.6 format .imodel by default. Also have you tried the Bentley Automation Services with MSTN CONNECT? It will publish all the DGN files on PW to an i.dgn or .imodel 1.6.
If the DGN or i-model path has spaces use quotes. Sample command for non PW session is here:
I appreciate your feedback but you have already stated that this can be done with no issues. I am requesting a solution for the application to access ProjectWise. So far, between the SR I filed and this forum, I still do not have a solution. I am starting to question if Bentley even knows how or if this can be done even though it was stated in the documentation. My apologies if I sound negative but I am frustrated and have started looking for an alternate solution.