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?
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.
so I can successfully publish a .i.dgn to .imodel but I cannot get it to log into PW and pull data down. Not sure what it is looking for in regards to "datasourcename" for the pwDatasource switch.
the keyin should be PUBLISHDGN CREATEDGNDBIMODEL 1.5
PUBLISHDGN
CREATEDGNDBIMODEL 1.5
this would set it to publish in version 1.5 and you can try running the keyin publishdgn publish force.
Mark Winegar said: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.
Have you tried to use the configuration variables to load the settings file you want to use. There is the variable MS_PUBLISHDGN_DESIGNLINKS see the following:
https://docs.bentley.com/LiveContent/web/MicroStation%20Help-v15/en/GUID-4B45DC72-397C-5E99-74DE-C66937D56BE3.html
Hi David,
PUBLISHDGN CREATEDGNDBIMODEL 1.5 is responding with "The output file name must end with .imodel". The keyin is acting like that is the name of the file and now needs an extension before proceeding. Also the 1.5, 1.6 and 2.0 if usable are hidden in the keyin dialog. If I put anything behind the initial keyin it must have the file name and extension.
CREATEDGNDBIMODEL 1.5 is responding with "The output file name must end with .imodel". The keyin is acting like that is the name of the file and now needs an extension before proceeding. Also the 1.5, 1.6 and 2.0 if usable are hidden in the keyin dialog. If I put anything behind the initial keyin it must have the file name and extension.
I have not set the variable to define a default settings file. The issue at the moment is that the settings file is not honoring the version defined when the settings file is saved and then reloaded into the publish dialog.
Hi Mark,
Let me work with David and a few other colleagues to see if we can get the version to be honored.
Thanks,
Dan
By default MSTN CE only publishes to the latest .imodel format using the key-in 'publishdgn createdgndbimodel', as per the latest version of ItgDgnDbImporter available on a machine. If someone wants to publish to an older format with multiple versions of ItgDgnDbImporter installed, then we can use IDgnToIDgnDb.exe separately from "C:\Program Files\Bentley\ItgDgnDbImporter 1.5" with command like "C:\Program Files\Bentley\ItgDgnDbImporter 1.5\IDgnToIDgnDb.exe" -i C:\ABC.i.dgn -z c:\ABC.imodel --imodelVersion 1.6. It could be 1.5 also, but do remember the case sensitivities while using the command. We could add this option by default with MSTN key-ins in future updates but right now it is not possible.
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.
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.