MSTN update 16
Pictures says it all.
Is it a bug or feature (that extended elements have no properties)?
Hi Ivan,
Can you please provide the dgn file for testing and let us know what software created those elements?
Regards
Maria
Maria Garcia
i did not create it but i bet it was bentley concept station.
i cant upload it here because its company data.
You can upload it to this sharefile link I create for you https://bentley.sharefile.com/r-r7f03a81eaa8846fbbffcd95141757289
I can follow up with you via SR if you wish
i have uploaded
Thanks Ivan I have received your file and I can reproduce the same. I will contact development for feedback and go back to you again.
I created SR7001303139 to follow up with you.
I can reproduce the issue in CONNECT update 16, but I can see property details in V8i SS10. See screen shot.
Please review screen shot and let me know if those are the properties you were expecting to see
I have agreed with development to file a Defect on your behalf. Bug 706659
Maria Garcia said:Please review screen shot
Even though it is not a source of the problem, but I am curious how the design file was created. I do not remember when I see such high element id... ;-)
Regards,
Jan
Bentley Accredited Developer: iTwin Platform - AssociateLabyrinth Technology | dev.notes() | cad.point
Hello, I am not sure but i suppose it was created in OpenRail Concept Station
yes its the properties
Ivan Galik said:i suppose it was created in OpenRail Concept Station
Thanks for the information. I do not know how OpenRail Concept Station works (only that it is not based on the same engine/technology as MicroStation, but iModel / iTwin.js), so the data must be imported into ORD.
Extended element is general purpose DGN V8 element (in fact, there are 2: graphical and non graphical), and for every type of element (e.g. parametric solid in CE), proper "enabler" has to be available. So maybe the enabler for the data is not available, or, the file is corrupted, so the right enabler is not identified.
From what is displayed in V8i I am surprised, not only because of high element id (but it's is not error), but also because of "Last modified" data. It is set to 1.1.1970, which means it was not set, because 1.1.1970 is "start time/date", when this information is calculated from.