Hi @FJankovsky
As you already know, DGN's are not like DWG's.
A DGN has Levels where the linework resides. The Levels manage the linetype, line weight, etc. They are akin to AutoCAD layers.
Here's a super oversimplified example: A dwg may have LAYERS for Proposed Objects, Existing Objects, and Objects to be Demolished. Each of those object groups may reside on its own Layer and each Layer may have its own linetype, line weight, and color. A dgn, however, will have Levels. Those Levels, like Layers, host the dgn's objects. You can MANAGE those Levels when the dgn file is OPENED, not MAPIMPORTED.
What does this mean? It means you might not need to MAPIMPORT on a dgn because you can simply 'Open' it using M3D. See image below.

It can be tricky to do this if you're NOT the author of the dgn. The MAPPING part, where you tell AutoCAD a Dgn Level must land on a specific Map3D Layer, might involve guess work. If you guess correctly, or you use good judgement to map the Levels, you can facilitate a good transfer from the dgn format to dwg. Or you may simply accept all the default values and just open the dgn without any custom mapping.
As far as using MAPIMPORT to create Object Data by selecting an entire column goes, that's not possible. You'll need to do that line-by-line. Using MapImport is the down-and-dirty way to add dgn linework. Opening a dgn and managing the Levels is much more sophisticated--it provides the opportunity to MAP Levels-to-Layers.
Chicagolooper
