[OR 2020 R1] Aliases not detecting offset profiles

Hi all

Has anyone been able to use aliases in annotation groups since the release of 2020 R1?

When annotating profile sheets, the list of alias targets is now blank and does not detect any profiles to annotate:

For one of our users, the alias list for superelevations is also blank.

Has anyone else had this issue? Is there maybe a workaround?

Kind Regards

Warren

Parents
  • I haven't seen this issue but I asked around to some colleagues and they suggested swapping out of that model and coming back in.  Maybe changing the active model to the 2D or 3D design model and coming back to your profile drawing model.  In doing this, the program can rescan the model and sometimes it helps to repopulate the fields.

    I also searched around the communities and found a post from last year with a previous release that may be similar to what you are seeing: https://communities.bentley.com/products/road___site_design/f/geopak-inroads-mx-openroads-forum/181590/exporting-superelevation-data-from-openroads-designer-superelevation-band-in-profile-band/542928#542928


    For more information about the Road and Site design tools, visit the Road and Site design WIKI at: http://communities.bentley.com/products/road___site_design/w/road_and_site_design__wiki

  • Thanks Chris, we'll try this.

    This has happened in three separate office though, on existing and new projects so it seems like the bug is quite easy to trigger.

    What I've found is that drawing sheet dgns that had been created before 2020 R1 and had had their profiles annotated are unaffected. New profile drawing dgns created in 2020 R1 seem to be more susceptible.

  • Hi Warren,

    Have you upgraded your Annotation Groups to 2020 R1? We have resolved some issues like this by upgrading our Civil Standards to 2020 R1 and then using the new Update Standards from DGNLib to sync the DGN back to the library.

    Regards,

    Mark


    OpenRoads Designer 2023  |  Microstation 2023.2  |  ProjectWise 2023

  • Hi Mark

    What steps do you do for this? What I've done is to open all of our existing dgnlibs in 2020 R1 and then save settings.

  • via Explorer like this:

    Regards,

    Mark


    OpenRoads Designer 2023  |  Microstation 2023.2  |  ProjectWise 2023

Reply
  • via Explorer like this:

    Regards,

    Mark


    OpenRoads Designer 2023  |  Microstation 2023.2  |  ProjectWise 2023

Children
  • Thanks Mark.

    I went through all of the feature dgnlibs as well as the sheet definition dgnlibs and did this. I created a brand new dgn for creating profile sheets and the alias targets are still blank. I can't think of what else it could be. SR created.

    Kind Regards

  • Hi Mark,

    The new sync from dgnlib functionality added in ORD 2020R1 is great for updating dgn files.

    However, you have also suggested upgrading the Annotation Groups to 2020R1. How exactly do you do this? Is it just matter of opening and closing the dgnlib file that contains the Annotation Group? I wouldn't have thought running the sync from dgnlib here would make sense since these elements are defined in this dgnlib file. Also, do you open the dgnlib in your usual workspace for edits or in no workspace to avoid contamination from other dgnlibs?

    For example you have standard dgnlib file i.e. ANZ-Design-Feature-Definitions.dgnlib from 2019R2Refresh perhaps with some custom added Annotation Groups and Definitions for profile frame annotation. If such custom made Annotation Groups and Definitions where based on original items (2019R2Refresh) that in 2020R1 workspace where updated to include additional functionality then do we need to re-do the customization from scratch or perhaps manually update the details that were changed?

    Regards,

    Mariusz

    Regards,

    Mariusz


    OpenRoads Designer 2022 R1

  • Hi Mariusz,

    That's right, simply opening the files will upgrade them. I'm suggesting syncing standards to the dgnlib in your file after you have upgraded your dgnlibs. As you said, it doesn't make much sense otherwise.

    I usually have our dgnlibs opened in our workspace as we have a Company workspace that overrides some of the symbology of the ANZ workspace, but doesn't have to be this way. I just do this to see how everything is interacting together.

    Regarding your example, I wouldn't expect you would ever need to recreate anything from scratch after a version upgrade.

    Regards,

    Mark


    OpenRoads Designer 2023  |  Microstation 2023.2  |  ProjectWise 2023

  • Hi Mark,

    Thanks for clarification. It's important to have clarity on the workflow as small details can make difference.

    Thanks for sharing.

    Regards,

    Mariusz 

    Regards,

    Mariusz


    OpenRoads Designer 2022 R1