When a datum export job is scheduled to run, either by recurring schedule or ad-hoc, the job configuration is copied to the solarnet.sn_datum_export_task to create the export "task". Currently that table does not have user ID or token ID columns, but the get-DatumExportTaskInfo-for-id query does a join back to solaruser.user_adhoc_export_task, solaruser.user_export_task uet, and solaruser.user_export_datum_conf in order to get the associated user ID and token ID values.

It would be much more staight forward if the user ID and token ID were added as columns to the solarnet.sn_datum_export_task table, so the association was clear and there were no dependencies back to the 3 user tables to resolve those values.