Users cannot define an export path for i.dgn files. It is usually created in the same directory as the original files, and the same is true for any attached reference files. However, while working in a Projectwise Managed Environment, our Project Directories are carefully curated, and we do not want to maintain imodels in the same Project Directory. It would be beneficial to provide the ability to choose the export location for the intermediate i.dgn files. In addition, when you publish an imodel with multiple attachements hosted from Projectwise, it takes a longer time because OPM forces the i.dgn files to get uploaded to PW without allowing the user to only save them on their local drives.
Hi Sujaan, Got your point. We are consuming this functionality in OpenPlant Modeler from MicroStation. So I am transferring this idea to MicroStation Ideas portal for review.
Hi Waqas,
I tried 3 times to upload my response and the idea portal wouldn't post my response. There is a glitch.
* How can you automate this for hundreds of models? Our interface partners require individual models separately and not packaged as one. I would like to specify the output location for the 100s of intermediate files.
* Secondly, when you create a single package imodel of a DGN that has multiple reference while working in a PW environment, OPM forces all the intermediate files to be uploaded to PW. This happens even if "Remove Intermediate Files" is checked. This takes unnecessary time depending on the users upload speed, for files that are eventually going to be deleted once the package is created. This can be improved.
With best regards,
Sujaan Fareed
Hi Sujaan,
Thanks for posting the idea.
Have you tried publishing by enabling the option to create a single package. This gives you the option to select export location.
Regards,
Waqas