When I open DGN outputs created by OpenRoads the Text Favourites do not display in Microstation Connect. This affects all outputs including Long Sections, Cross Sections and Control Lines
I have tried using the same workspaces and ensuring that the Text Favourite Variable is mapped. However if I open the files with OpenRoads or OpenBridge with no workspace applied, I am able to see the text favourites. It is just Microstation Connect (Edition 12) where the Text Favourites do not populate with any data.
Thanks for your reply. Let me clarify,
Text favourites work with no issue in OpenRoads and ORD is mapping to the dgnlib.
It is when I try and open the ORD outputs in Microstation Connect that the text favourites stop working. MS Connect is also mapping to the same dgnlib with the text favourites in it.
i also have this issue, did you find a resolution?
I logged a ticket with Bentley and this was an issue however it has been resolved in Microstation Connect Update 13.
I have upgraded now and no issues.
So is MicroStation being correctly mapped to the Text Favorites file alone, or are y'all dropping the text in order for MicroStation (not ORD) to display it correctly?
Please see below for the response Bentley gave me.
I didn't use Bentley's workaround as I didn't want to disable fields. By upgrading to the new Connect Update 13 however it has solved the problem for me. I had tried having it mapped to the text favourites but this didn't do anything as it was a problem with the software.
I have discussed this issue with an analyst specializing in OpenRoads CONNECT Edition and they mentioned that MicroStation CONNECT Edition does not understand how to evaluate OpenRoads Text Favorites but it tries to and fails. If you set MS_AUTO_UPDATE_FIELDS = NEVER then it will retain the last used value that was in OpenRoads. This variable has to be defined before any of these files are opened in MicroStation CE otherwise it will not display properly. Apparently MicroStation CE Update 13 will not try to evaluate OpenRoads text favorites so it should not be needed from then on.
Thank you so much for this bit of information; much appreciated!
Indeed, I have been defining the Update Fields variable in just this manner because I have have run into these conflicts between MicroStation CE and ORD (currently running ORD 2019 R1). Of course, I do not desire to use this variable in this manner because it causes MicroStation to not update fields when I desire it to do so; outside of the ORD fields, of course.
So happy to know that MicroStation will ignore these ORD fields in the latest updates!