View Issue Details

This bug affects 1 person(s).
 6
IDProjectCategoryView StatusLast Update
16374Bug reportsImport/Exportpublic2021-03-29 16:22
Reporterrudydehaas Assigned Toollehar  
PrioritynoneSeveritypartial_block 
Status closedResolutionfixed 
Product Version4.2.5 
Summary16374: attributes disappear on import
Description

I added six attributes to the cpdb so the first line of my import file looks like this:
email;firstname;lastname;coursename;coursenumber;faculty;instructor;section;session

(Note that firstname is actually a unique numerical id to get around the fact that I need to send the same people multiple questionaires - one for each course they take.)

I deleted one at a time using the gui the 3 participants I had manually entered to test this. On importing a test of 539 rows the system did not recognize that the new attributes existed, and added six copies. On Display Participants none of these additional attributes showed up - all blank after "Blacklisted" - note creation date is blank too.

PHPmyadmin shows all 12 attributes in Table: participant_attribute_names ; 6 marked visible=true, 6 false. Table: participant_attribute does seem to have the imported values.

Question 1 has default answers = the six new attributes, but only works for {TOKEN:lastname}, one other shows css, the other four are blank.

Steps To Reproduce

See above - or email me (rudy@wadocan.org) and I'll give you an admin login to the survey.

TagsNo tags attached.
Bug heat6
Complete LimeSurvey version number (& build)Limesurvey4.2.5+200526.tar.gz -
I will donate to the project if issue is resolvedNo
Browserfirefox under gnome (default for debian)
Database type & versionmaradb
Server OS (if known)debian 9
Webserver software & version (if known)apache2
PHP Version7.2

Users monitoring this issue

There are no users monitoring this issue.

Activities

rudydehaas

rudydehaas

2020-06-09 18:18

reporter   ~58228

So.. I used phpmyadmin to delete the 539 new participant records, the lime gui to set attribute visibility to true for all 12 (6 real, 6 new) and then deleted the ones that did not show as "name ()" - e.g. there were two versions for coursename: 1 - "coursename ()"; and "coursename (coursename)". I deleted all those that looked like the second version. Then re-imported. This time the drag to "Drop a CSV field into an existing participant attribute listed below to import your data into it." worked -although the new attribute names did not show there - and so did the upload.

Three additional comments:
0 - this is a bug and not just me being stupid.. (right? ?)
1 - we need to be able to add participants in bulk without the people doing it having the skills to mess with the db directly; and,
2 - a bulk delete fn would be nice to have - as would the ability to extend the table key to guarantee unique values without having to kludge it as I have here.

rudydehaas

rudydehaas

2020-06-11 19:00

reporter   ~58256

upgraded to 4.2.8 this morning.
1 - attributes exist in pariticipant table
2 - attributes load correctly into CPDB if I delete the rows and re-create the attributes as part of the bulk upload. New records added later show no values for the attributes.
3 - csv file exported from CPDB has attributes, deleted on import to participant table for survey,. Again work around is to delete attribuites, then load from csv.
4 - direct transfer from CPDB shows attributes, by name and in correct order, during -pre-load process, but values get dropping during the process.
(This may be me doing something wrong, I see no way to duplicate here the attribute creation/mapping you see during csv import)

ollehar

ollehar

2021-03-10 17:11

administrator   ~63053

You're using an outdated version of LimeSurvey. Please update to the latest version and check if the bug can still be reproduced. Thank you.

rudydehaas

rudydehaas

2021-03-10 18:07

reporter   ~63126

This was fixed, and reported fixed, some time ago.

c_schmitz

c_schmitz

2021-03-29 16:22

administrator   ~63710

Thank you for the feedback!

Issue History

Date Modified Username Field Change
2020-06-09 17:53 rudydehaas New Issue
2020-06-09 18:18 rudydehaas Note Added: 58228
2020-06-11 19:00 rudydehaas Note Added: 58256
2020-06-11 19:00 rudydehaas File Added: Screenshot from 2020-06-11 09-55-04.png
2021-03-10 17:11 ollehar Assigned To => ollehar
2021-03-10 17:11 ollehar Status new => feedback
2021-03-10 17:11 ollehar Note Added: 63053
2021-03-10 18:07 rudydehaas Note Added: 63126
2021-03-10 18:07 rudydehaas Status feedback => assigned
2021-03-29 16:22 c_schmitz Status assigned => closed
2021-03-29 16:22 c_schmitz Resolution open => fixed
2021-03-29 16:22 c_schmitz Note Added: 63710