Columns Dropped on Export.

[ack_ack_ack_ack]

I'm attempting to export a joined table so the join isn't in memory.  I am required to do this because in-memory joins are not supported by the web-based "Stories" app/thing.

The first screenshot shows the point column station_point.  It draws points on a map as expected.

Any attempts to export/convert the data results in the station_id and station_point column being deleted.  As shown below. 

I need the point drawn on the map. Instead, I'm left with metadata attached to nothing.
There's no error.  The data is useless without the station_point column.  I can live without the station_id column.  No idea where it went, though.

[SSWoodward]

Can you share what tools you are using to export your data? 

Exporting using export features should include the geometry and provide the opportunity to access and edit the field map to define the output table.  The behavior you are describing seems consistent with export table, which will create a non-spatial dataset, a table, and drop the geometry columns.

Hard to tell from the image and details provided, but it seems like this dataset may be a non-geodatabase feature class with the "stations" column marked as the unique ID field, is that the case? If so, it is being overwritten with the object ID column in the output because unique ID's are arbitrary and are not meant to persist through export.  To maintain the values in your station field, map it to a new field called stations in the exported table.  Your table will then create with a new attribute column 'stations' and an OID field.  This article may be helpful.

[SSWoodward]

Instead of exporting a join, a relationship class may also be a viable path forward depending on your data structure.  Check out the relationship class doc to see if it might suit your needs better than exporting a join.

Relationship Class Fundamentals