View Issue Details

IDProjectCategoryView StatusLast Update
15799Bug reportsImport/Exportpublic2021-03-10 22:20
ReporterMazi Assigned To 
Status acknowledgedResolutionopen 
Product Version3.22.1 
Summary15799: Token export uses wrong column names for invitation and reminder sent dates
DescriptionToken export file uses "invited" and "reminded" as column names for invitation and reminder sent dates while at the DB it actually is "sent" and "remindersent", see screenshots
Steps To ReproduceExport token details as CSV file and compare to DB layout.
TagsNo tags attached.
Complete LimeSurvey version number (& build)Version 3.22.x
I will donate to the project if issue is resolvedNo
Database & DB-VersionMySQL 5
Server OS (if known)Ubuntu 14 TLS
Webserver software & version (if known)Apache 2
PHP Version7.2.26




2020-01-29 16:35


export_columns.png (5,960 bytes)   
export_columns.png (5,960 bytes)   
db_columns.png (33,218 bytes)   
db_columns.png (33,218 bytes)   


2020-01-29 17:12

developer   ~55567

And when you import : you loose `sent` and `remindersent` data ?


2020-01-29 17:40

partner   ~55568

Nope, I tested with the sample from the screenshot and it imports the invitation sent date stamp fine. So there seems to be some kind of mapping?

I just stumbled upon that when trying to import a large CSV file directly into the token table using phpmyadmin. There it complained that the column name "invited" doesn't exist.


2020-01-30 07:35

developer   ~55569

It was same in 2.6 … and surely before.

My opinion : not a bug or an API broker.


2020-01-30 07:36




2020-01-30 14:48

partner   ~55574

Since import is working fine even with the wrong headings, I also think this is nothing urgent. But at a certain date someone must have added the mapping, for whatever reason?! Can we find that out?

My 2 cents is that if we are exporting the tokens from the database, we should also stick to the proper column headings so a direct DB import would still be doable.


2020-01-30 15:06

developer   ~55575

> But at a certain date someone must have added the mapping, for whatever reason?! Can we find that out?

It's why i check in 2.6lts …

Before 2.6lts ! too old …

Issue History

Date Modified Username Field Change
2020-01-29 16:35 Mazi New Issue
2020-01-29 16:35 Mazi File Added: export_columns.png
2020-01-29 16:35 Mazi File Added: db_columns.png
2020-01-29 16:47 cdorin Assigned To => cdorin
2020-01-29 16:47 cdorin Status new => assigned
2020-01-29 17:12 DenisChenu Note Added: 55567
2020-01-29 17:40 Mazi Note Added: 55568
2020-01-30 07:35 DenisChenu Note Added: 55569
2020-01-30 07:36 DenisChenu File Added: Capture d’écran du 2020-01-30 07-36-46.png
2020-01-30 14:48 Mazi Note Added: 55574
2020-01-30 15:06 DenisChenu Note Added: 55575
2021-02-04 10:15 cdorin Status assigned => new
2021-02-04 21:20 cdorin Assigned To cdorin =>
2021-02-04 21:20 cdorin Status new => acknowledged
2021-03-10 22:20 ollehar Priority none => low