Importing a Drawing Model into another file

Why are you using Drawing models? They are pointless and you could compose your drawing directly referencing your design model to the sheet.

However, have you tried referencing the Drawing model with Live Nesting = 2 ?

I suspect OP is using Drawing models in part because ORD defaults to creating drawing models for their sheets, especially since there AREN'T any profile or cross section design models anymore.

OP, Barry is right that you CAN create your detail and annotate it in the design model. We did that for YEARS before the introduction of the drawing model (and even years after, because it worked) It simplifies things because the detail model is then self-contained, and we only needed to keep track of one item instead of two. It was a design model, with the Annotation Scale set to the desired plotting scale of the detail. Annotation scale not only handled text/dim sizing, it also accounted for any scaling up or down onto the border in the sheet model. Since MicroStation can handle any number of design models, we could create sheets of many differently scaled details by creating a design model for each scale we would be using. It seemed easier than keeping the linework of an individual detail separate from all the annotation, and it made scaled details very simple. You could also import a detail from one project to another very easily (one model, ready to go, bang).

I think Saved views are part of the design file, and not actually part of any model. Again, not something I use often yet, but I know there are non-graphic/semi-graphic design file data that isn't model based, and that may not get imported with any (or all) models.

I’m not in the position to test atm but I can’t think of a reason why you aren’t seeing references. A drawing model after all is just a design model restricted to 2D with a different background colour. Can you upload a test packager file?

MaryB said:

I suspect OP is using Drawing models in part because ORD defaults to creating drawing models for their sheets, especially since there AREN'T any profile or cross section design models anymore.

Do you not get the choice of model type in ORD?

No...Or at least, not if you want the software to create your sheets for you. As I understand it, the process is hardwired to work a certain way. You can certainly work around it in a lot of ways, but not when it comes to cross sections or profiles. There are no graphic cross sections or profiles created anymore -  (as I understand it) they are saved view references of a section cut through the 3D design model attached to a drawing model. I mean, you can take that and generate graphics from it, but from that point, it's not "live" anymore.

I've been working through training, but I don't have any actual projects in ORD. My state hasn't adopted it yet, and I'm not about to do the work to create all the standards that would be required for successful production. I'm still wrapping my head around all the ways this design/production method is different, and trying to plan how I'm going to break the news to my department.

I agree - OP, a test file of what you have would be very helpful, if you have generic detail set up this way. We could take a look at how it's done and see what we might figure out to help.

I do appreciate you both willing to look at a file.

If you simply attempt to copy the Drawing model 'Drawing_SHT1007C_OutletDetails' you will see what I'm talking about.  It works the same way if you attempt to import that same model into another file.

I have determined it's not related to the saved view.  There are no saved views in the file.  I have figured out however, if you reference the same model above back to itself using the any of the named boundaries within the model and then try to copy the Drawing model it will keep the references attached.  I'm assuming it would also work if you just had a reference in the drawing model that was attached via named boundary or possibly a saved view.  Seems like it has something to do with how the reference is attached specific to the Drawing Model because I can't replicate the behavior in a Design model.

Thanks for coming down the rabbit hole with me...appreciate it.

Jamie

TestFile_EnglishForeSlopeProtectionBridges_Connect.dgn

Morning Jamie,

As I suspected, I had no problems whatsoever attaching your details using V8i. When I attached the model, I first see the 'Live Elements' drawn in that model (annotations in this case) and as I wrote in my original reply, setting Live Nesting to 1 was enough for the Linework etc... to become visible (2 would be required if you had a deeper level of reference nesting). No fussing about with Named Boundaries, just regular consistent reference files behaviour I deal with all the time.

Are you not seeing the same behaviour in CONNECT?

Morning Jamie,

As I suspected, I had no problems whatsoever attaching your details using V8i. When I attached the model, I first see the 'Live Elements' drawn in that model (annotations in this case) and as I wrote in my original reply, setting Live Nesting to 1 was enough for the Linework etc... to become visible (2 would be required if you had a deeper level of reference nesting). No fussing about with Named Boundaries, just regular consistent reference files behaviour I deal with all the time.

Are you not seeing the same behaviour in CONNECT?

I see the same behavior in Connect.  My problem is when I try to copy that Drawing model it completely detaches the reference. That's all I was curious about and wondering why it's detaching the reference.

I understand all these other workflows would work...was just wondering why the one I was testing is not.  

Thanks for digging into this.

Jamie

I still don't see the problem:

That's interesting.  I think it's an OpenRoads Designer issue.  I tried to open the file using straight microstation and it works.  Thanks for the nugget.

Jamie

Not unheard of for ORD to have bugs that aren't in regular MicroStation. The "Power Platform" isn't exactly the same as MicroStation, and it's often a version or more behind. And the older the version of ORD you have to use to meet client standards, the further behind the bug fixes are.

No problem. At least you can temporarily load up MS to do that operation and swtch back over to ORD until (if) it gets fixed.