Break.doc
Hi
We are experiencing a major problem with database linkage on elements. When we use the command 'Break element' and break eg. a line in two parts the database linkage is gone on both parts.
It's vital for us that both parts keep the database linkage as it does in MicroStation V8i.
My database settings is set to this:
In the attched file a have two lines. One is not broken and the database linkage is retained. One is split into two lines with break element but here the database linkage was deleted.
You can see if the database linkage is ok by using the keyin: 'analyze element'
I'm not able to upload dgn files, so I have renamed it to.doc (tried in both Google Chrome and IE11 but it is same problem).
Please rename the file to .dgn.
Are we doing something wrong or is this a bug in MicroStation CONNECT? It is tested in both update 4 and update 6 with the same result.
Best regards
Rune H. Christensen
You mentioned that you have attached files. These don't seem to have been included. Would you be able to attach these again.
Is this issue being reported for the latest release of MicroStation CONNECT Edition (Update 6)?
RegardsAndrew BellTechnical SupportBentley Systems
Hi Andrew
Thanks for answering. We have been testing on this issue on the latest versions of MicroStation CONNECT, but still we have this issue in Update 9. The attached file "Break.doc" must be renamed to Break.dgn before opening. When I created this ticket it was not possible to attach dgn-files, so I must rename the file.
I hope that this issue can be fixed soon.
Regards
There still does not appear to be any files attached to your post. You might like to attach this via the Secure File Upload.
https://communities.bentley.com/help/w/be_communities_help/7079/communities-secure-file-upload
Andrew Bell said:There still does not appear to be any files attached to your post
I see Break.doc in the OP, right at the top.
Regards, Jon Summers LA Solutions
This error was corrected in earlier versions of CONNECT Edition, but sadly it seems that it has returned in CONNECT Update 17.2... Hope it's possible to fix it again...