This post just popped into my mind as it’s related to ongoing conversation about Central’s submission storage strategy and a Central bug you reported. The
SubmissionDate is injected by Aggregate when it reassembles submissions. Central does not modify incoming submissions in any way. We’d have to make a separate Central API request and find a place to store the submission date to have it available for export.
You and I have talked a bit about Central-Briefcase in another thread. As I mentioned, we consider direct exports from Central the primary way to get CSVs out so we wouldn’t prioritize this. If someone wanted to take it on we could talk through possible approaches. The Central export has
SubmissionDate and the same format as the Briefcase export.
I think your major barrier to directly using the API was a bug that affects certain forms with repeats. Thanks to you sending me your form, we have a fix that should be released shortly. I’ll be sure to tag you once it’s available. In the next Central version, we’ll add an endpoint to request just the root CSV (as opposed to the zip of all data) and may do the same for repeats if there’s demand.