There are different ways to add attributes to AutoCad entities. The esteemed Mr @Pointdump has shown one. The choice you make, you have more than one choice, is dependent upon the type of AutoCad objects you wish to export.
Civil 3D entities are not considered to be exportable entities and are not good candidates for shapefile or Gdb. Don't get me wrong, C3D is excellent for purposes such as, but not limited to, civil infrastructure design, surface creation and volume analysis. Exporting them to ESRI feature data objects could present issues to GIS users. Many civil users resort to the EXPLODE command to make civil objects exportable simply because they want to get job done. Exploding, however, creates disjointed entities from objects that were once whole and separates the disjointed pieces from their data.
If you wish to export to shapefile, then adding attribute data or fields means you are populating the shapefile's database file or dbf. There are two basic sources from which to gather data that can be added to the dbf.
SOURCE 1:
This source gathers the Properties of AutoCad entities. The properties of AutoCad objects, as you already know, can be displayed in the Properties palette. For example, if you select a closed polyline, the properties palette will dispaly the area, length, and layer. These inherent propeties can be added, or harvested, when exporting closed polylines to shapefile.
If your closed polylines are parcels, then area and the length of the outline is likely to be harvested while linetype and line weight properties wouldn't be helpful so those properties will be ignored. If residential parcels are on a layer named RESI and commercial parcels are on a layer named COMM then harvesting the AutoCad layer property would be a benefit to the shapefile's dbf due to the layer's descriptive nature pf the layer's name.
Your creativity and foresight into how you organize your drawing can play a huge role in harvesting inherent data for your shapefile's dbf. As you can see, drawing organization with the intent to export to shapefile is not always consistent with the way we draw in AutoCad, especially when drawing civil entities in C3D.
SOURCE 2:
This source taps into an Object Data table. This table is created by you. You determine the fields you want then you add those fileds to your table. A single drawing can have multiple tables. The fields can be integer, character, point (coordinates) or real. Once your table is established, you add the table to your objects (these objects will become your feature class) and once they're added, you can fill-in, or add attribute data to the fields. Populating the fields will create 'smart' AutoCad entities because unlike vanilla AutoCad entities, smart entities hold data--they have object data attached to them. This object data is in addition to the object's properties, not a replacement of the porperties. When smart objects are exported to shapefile, the object data that's attached to them can be exported along with the AutoCad entities--the objects become the shp and the object data is added into the dbf.
When exporting AutoCad entities, you may harvest both the inherent properties and object data. Adding attribute data is not a one step process. There's no single mouse click that can create, write, store, gather and export attribure fields that'll be viewable in Arc Pro. If you can describe in detail, what kind and type of AutoCad entities you with to use in Arc Pro and what you expect to see once your data table in Arc Pro is opened, then a suitable workflow can be given that will accomplish your goal.
Chicagolooper
