Hi,
this is partially funny, partially annoying situation: When trying to export V8i project from GSA CE, this message is displayed:
But how the index can be removed, when GSA does not display this node anymore?
Of course it can be solved to open the project in GSA V8i and to removed the node, but this is bad workflow, especially when GSA CE asks for approval to update the project when its opened for the first time. Does it mean the project is updated, but in fact not updated, because not supported parts are still there?
With regards,
Jan
We apologize for this, we should have caught this one before the release. It will definitely be fixed in the next release schedule in a couple of months. In the meantime, you are right, the only workaround is to use the V8i GSA to first remove the reference files index.
The workspace behavior has changed in the CONNECT environment. The first export effectively fixes this in the schema. It should also have fixed the reference file index, but obviously something goes wrong. For files without reference files index, the export correctly fixes the workspaces.
Sorry again
Yves Boivin
Hi Yves
Yves Boivin said:The workspace behavior has changed in the CONNECT environment.
yes, even in MicroStation a migration requires huge redesign of customers' configurations maintained for years. I guess Bentley Map will be even bigger challenge ;-)
Yves Boivin said:the only workaround is to use the V8i GSA to first remove the reference files index
I did, but I ended with weird error message from Bentley Map, not able to even open dialog and browse files. I guess it's because the export in V8i is done outside standard BM workspace location and customized shortcut with startup parameters (defining this specific workspace location) is used, so some manual modification will be required also in CE project.
Bentley Accredited Developer: iTwin Platform - AssociateLabyrinth Technology | dev.notes() | cad.point
I will have someone running the same steps here right now. I will reply with the result as soon as possible.
Thank you for your time
Yves
Yves Boivin said:I will have someone running the same steps here right now.
My current assumption it's caused by some specific setting in original project. It will require some analysis on my side to be able to identify how workspace is created and with what parameters BM is started,
Regards,
Unfortunately we will have wait for more feedback from you. We are not able to reproduce your problem here. With the extra tests we have done here today, the suggested workaround works fine.
Hi Yves,
I made a step forward.
The original error message was:
The message itself is correct, from some reasons dgn folder was not created in exported workspace. But I am a bit surprised missing folder is enough to block Open Design File dilaog to be opened.
In this project dgn files are stored separately from exported structure, so in V8i workspace there are also separated workspace (stored locally) and dgn files (stored on network drive).
After I created dgn folder manually, BM starts. More configuration changes will be required to be able to test the project, at least to configure all DB connections etc. to be equal in 64bit as they are at 32bit drivers.
Hello Jan.
you probably aware of this, but If you activate "verbose" as option, you will be able to see what went wrong, on exporting file, in the message center of Geospatial Administrator. I do not reproduce on my side. where do you set that specific path ? It seems to be DGN source files.
Thank you.Sebastien