I’m trying to populate my DEV instance table with data from my PROD instance table. The CSV export can’t be imported because the date format isn’t recognized.
Is there a best practice I’m missing?
Here’s some data from the CSV:
Jul/17/2023 08:39:37 -04:00
Jun/26/2023 09:14:24 -04:00
Sep/27/2023 12:09:20 -04:00
And here is the similar from the Tulip Table, but different format:
After deconstructing and reconstructing in excel to get the formatting right, I’m still getting this error:
Does the uploader not accept datetime and only date?
James - great suggestion and something that has been on the team’s radar actually.
good and bad news - on an upcoming release the CSV importer will support a lot more datetime formats and make this much easier (and make it so the datetime exported from CSV can be recognized by the CSV import) - but I know you are on LTS 8.2 so this won’t help you (yet!)
@jmlowden Quick update here: With the latest release, we have shipped an update to supported Datetime formats that are supported. This significantly increases the number of formats that will be accepted by the import.
As @Beth said, this will unfortunately not help you just yet due to LTS. But I wanted to still keep you updated to you are aware of what will be coming your way at some point.
I just tried to export completion data from an app then extract the needed data and import the modified CSV to a table. The CSV importer does not accept the default datetime export format of “2024-07-30 08:30:00 -04:00” as a valid date format… very frustrating.
Hey @Alinator, sorry to hear that you are running into issues. I just did a quick test on my end and am not able to replicate what you describe. If I export completion data, I can select timestamp fields in the CSV upload configuration and they are interpreted correctly - both the automatically generated “Start Time” and “End Time” fields as well as those related to variables.
Could it be that during your modification of the CSV there is a change introduced to the timestamp format?
Thanks for the reply @stefan it is possible the problem was induced during my editing process, but I’ve already completed the project by converting to the ISO8601 date format and I can’t commit any more time to troubleshooting or reproducing the issue at the moment.
I’ll reply here if I run into an issue again in the future and figure out the cause.
Has this problem resurfaced? I am unable to import rows that How to Import a Spreadsheet into a Table indicates it should be supported. I’m still on LTS 11 but this thread suggests this should be working.
We added support for about 30 more formats in r265, which is 3 releases after LTS11 (r262). The only format supported in LTS11 is ISO 8601 and RFC 2822.
Does it support importing the default datetime format applied when the Validation feature flag is enabled? Perhaps this is not an issue in newer LTS, but in our old LTS, the CSV export from instances with Validation feature flag enabled use the following format, which is not supported by the CSV uploader:
