[OR 2020 R1] Aliases not detecting offset profiles

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

Hi Chris

We've tried switching between 2D and 3D views and then back and forth between models, but the targets are still not appearing in the lists.

I've switched to the delivered configuration and I added aliases and rows pointing to those aliases in the delivered annotation groups. I encountered the same problem, so it's not something wrong with our dgnlibs or annotation group settings.

Right now, this means we can't use ORD for profile plan production anymore.

Kind Regards

Warren

Hello Warren,

Make sure the target you’re expecting to select/see in the dropdown list should be displayed in the single Profile View Window.

In the attached video (apologies for not having audio in it):

• First Attempt is made to create a profile drawing using the existing ground profile.
  - Where you won't see any profiles listed in the dropdown to target.
  
  
• The second attempt is made by proposing a profile. (It’s displayed in the Profile View window).
  - Now you can see the Proposed Profile is listed in the Dropdown.
  
  
• In the last Attempt, I made bringing the EOP profile into the Profile View Window using Project Tool.
  - This time you can see the EOP listed in the Dropdown to target along with other profiles that are displayed in the profile view.
  
  
  
  

Hi Kiran

Thanks for the very detailed reply. I see that your dgn is called "Geometry and Corridor" and then you use the annotation group within this same dgn.

In our drawing workflow (which used to work), my geometry dgn has the corridor referenced into it with edge of pavement profiles projected onto the main geometry. This geometry dgn is then referenced into a new dgn where the profile sheets are created from the referenced geometry. So I follow exactly the same process but with references rather than all in one dgn. Do the aliases show if you work with references?

Kind Regards

Hello Warren!

Do the aliases show if you work with references? 
-Nope.

The Profiles need to exist in the Master file i.e. the Profile production must be run in the alignment drawing or

The Profiles need to exist in the named boundary, create the named boundary within the alignment (profile) drawing for the Profiles to appear during plan production.

Hi Kiran

Thanks for the reply. This highlights the issue - before 2020 R1, you used to be able to work with referenced profiles. As in referenced profiles would appear in the list of aliases.

The workaround to address this bug does not make sense with drawing production workflows - you now need to have a copy of your geometry in a separate dgn in order to annotate alias profiles instead of it being linked to the geometry and corridor elements used to build the model.

I think this bug got introduced when other bugs relating to profile annotation were fixed (such as referenced profiles randomly becoming detached, which doesn't seem to happen anymore).

I've filed a SR on this issue, but I don't know if it's going to be addressed in the next update or not.

Kind Regards

So...the plans production method of referencing all of the design files into the plan sheet file doesn't work with offset profiles? There needs to be an entire different workflow for creating plan sheets with offset profiles? That's terrible, and it sounds like BAD design on the software side of things. Please make sure that the Bentley Documentation is updated with this crucial piece of information.

I know people who already don't like the new means of plan production and annotation, and telling them that they are going to have to learn TWO procedures is just going to make things worse.

Does anyone designing the program at Bentley HAVE any experience with production work anymore?

So...the plans production method of referencing all of the design files into the plan sheet file doesn't work with offset profiles? There needs to be an entire different workflow for creating plan sheets with offset profiles? That's terrible, and it sounds like BAD design on the software side of things. Please make sure that the Bentley Documentation is updated with this crucial piece of information.

I know people who already don't like the new means of plan production and annotation, and telling them that they are going to have to learn TWO procedures is just going to make things worse.

Does anyone designing the program at Bentley HAVE any experience with production work anymore?

That does seem to be the situation, yes. I do believe it's a bug though, because it was working wonderfully between Update 5 and 2019 R4.