I've been working on preparing company standard feature definitions, feature symbologies, annotation groups, and text favorites.
I've been preparing these features in working files, and now I want to import them into the appropriate dgn libs. Anybody know how I can update a dgnlib with specific features from another dgn?
Thanks
Do the appropriate DGNLIB files already exist with definitions that are already in use?If not, you can just relocate your working files to the proper directory and rename them to be DGNLIB files.
If so, this Help page may be helpful: https://docs.bentley.com/LiveContent/web/OpenRoads%20Designer%20CONNECT%20Edition-v13/en/GUID-6105A5EE-FDBB-4D27-BA54-D94AABB3ADC9.html
It looks as if you could open your DGNLIB file, then use the Explorer dialog to load your working file as a Temporary Library. From there you may be able to copy your features and such from your working file to the Library.
MaryB
Power GeoPak 08.11.09.918Power InRoads 08.11.09.918OpenRoads Designer 2021 R2
answer to your first question would be no... in my working file i made copies of similar out of the box definitions, renamed and adjust where needed.
I assume it should be that simple! How can I load my working file as a temporary library into my dgnlib?
actually found information where i can export/import feature definitions into an xml file. still looking for a work around for the annotative style i created(text favorites and annotation groups).
If you go toward the bottom of the page I linked, is shows how to load a temporary library by right-clicking on the OpenRoads Standards -> Libraries heading in Explorer.
Caveat: I have not tried this myself and I am not in ORD this week to confirm.
If that option is not available, it's possible that there is a bug, or that the Help file is simply wrong...In that case, you should probably file a Service Ticket with Bentley Support to let them know that's a problem. While you're there, you can ask about combining your resource libraries.
I know from watching people here that the XML option works fairly well for feature definitions. I don't know how else you would migrate the annotation-based definitions. Hopefully others here will have more suggestions.