MicroStation Connect Publish imodel version keyin

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?

Parents
  • 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.

  • 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.


    This is a test

  • 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.

    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?

     
    Regards, Jon Summers
    LA Solutions

  • 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:

    1. How is the Datasource found? What is to be used? Should it be in quotes, brackets, etc..?
    2. How is the nomenclature of the  "--input" supposed to work? Is it full path, is it path from Documents to source file folder, is it the DMS path and if so what does that look like? Should it be in quotes, brackets, etc..?
    3. How is the nomenclature of the  "--zoutput" supposed to work? Is it full path, is it path from Documents to destination file folder, is it the destination DMS path and if so what does that look like? Should it be in quotes, brackets, etc..?
    4. Is the "--temp" location required?

    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.

  • 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.


    This is a test

Reply Children
No Data