Write Geodatabase as DWG / DXF and include attribute in the export.

One way that works for me is to use the Map 3D Object Data writer. Make sure to check if it works using something like AutoCad to rule out issues with reading the data back in using FME.

Hi ​@nielsgerrits 

Thanks for the info - is there a particular way of configuring the Map 3D Object Data writer to ensure that the accompanying table data comes through in the export?

Thanks!

Nothing special, just write it as anything else. I find checking the hard part as my daily use of AutoDesk products was a long time ago. Created a sample workspace writing and reading back the written dwg with object data, see attachment.

Nothing special, just write it as anything else. I find checking the hard part as my daily use of AutoDesk products was a long time ago. Created a sample workspace writing and reading back the written dwg with object data, see attachment.

 

Many thanks ​@nielsgerrits, I’ll give this a go later today, and if I may, get back to you with any queries?

Cheers!!

Nothing special, just write it as anything else. I find checking the hard part as my daily use of AutoDesk products was a long time ago. Created a sample workspace writing and reading back the written dwg with object data, see attachment.

 

Hi ​@nielsgerrits  - I have tried your suggestion, with my Geodatabase file, and created 3 new attributes / fields, to test if they would all carry through, as follows:

The Table of the Attribute Exposer shows the following:

However, when I load the newly written Buildings_Tank DWG into FME I still get the following:
 

Does FME not support or read DWG data tables? As I don't have a CAD package, do you know if there’s any way that I can I confirm if all table attributes / fields are available within the file, please?
Thanks in advance :)

The FeatureReader and Exposer part is reading the data back in to prove the attributes are in the resulting file. I’m not sure why you add another writer after that, please just use an Inspector to inspect the result.

I’m not sure how you come to the last screenshot part but it looks like you are reading dynamic / generic. In this case you always need to expose the attributes. You can inspect unexposed attributes in the data inspector in the feature information window.

Hi ​@nielsgerrits - I see, my apologies, so the FeatureWriter writes the DWG file with the required attributes in place.

The last screen shot shows the result of me dragging the newly written DWG file on to my Workspace and running it - I was expecting to see all my attributes in the table, but the <no schema> heading confused me.

If I open the DWG file (the one written by the FeatureWriter) in AutoCAD, I should see a table of the following attributes?

Many thanks👍

...

...

If I open the DWG file (the one written by the FeatureWriter) in AutoCAD, I should see a table of the following attributes?

Many thanks👍

Not sure, but according to copilot autocad map 3d and autocad civil 3d can display this, but plain autocad cannot.

...

...

If I open the DWG file (the one written by the FeatureWriter) in AutoCAD, I should see a table of the following attributes?

Many thanks👍

Not sure, but according to copilot autocad map 3d and autocad civil 3d can display this, but plain autocad cannot.

OK - thanks ​@nielsgerrits