View Issue Details

Jump to NotesJump to History
This bug affects 3 person(s).
 16
IDProjectCategoryView StatusDate SubmittedLast Update
18919Bug reportsCentral participant databasepublic2023-06-23 15:012024-05-12 11:21
ReporterMagasB Assigned Togabrieljenik  
PrioritynoneSeveritypartial_block 
Status closedResolutionunable to reproduce 
Product Version5.6.x 
Summary18919: CPDB participants import makes duplicates
Description

When importing participants into the CPDB, there is an option which meant to be avoid duplications in the database by overwrite the existing records. This option does not work well: after the import, duplications appear in the CPDB.

Steps To Reproduce

Steps to reproduce

Import a .csv into the CPDB two times. The second .csv must contain different data fro the first one.

Expected result

The second import overwrites the original imported data, if the data is different.

Actual result

Duplicated participants appear in the CPDB with the same email, firstname and lastname.

TagsNo tags attached.
Bug heat16
Complete LimeSurvey version number (& build)5.6.26 + 230613
I will donate to the project if issue is resolvedNo
BrowserChrome
Database type & versionMySQL 8.1.2
Server OS (if known)Ubuntu
Webserver software & version (if known)
PHP Version8.1.2

Users monitoring this issue

khfischbach

Activities

gabrieljenik

gabrieljenik

2023-07-07 22:17

manager   ~75983

Thanks. Bug received.
Will try to reproduce it and be back.
gabrieljenik

gabrieljenik

2023-07-14 15:58

manager   ~76089

Duplicated participants appear in the CPDB with the same email, firstname and lastname.

Can you please paste a screenshot of the message that appeared?
Does it say something like "they were found duplicate using the id field" ?

Thanks!
gabrieljenik

gabrieljenik

2023-07-25 01:00

manager   ~76254

Please, can you provide 2 sample files as to reproduce the issue?
gabrieljenik

gabrieljenik

2023-10-23 20:42

manager   ~77894

As per the comments, will be closing the ticket.
Please add any comments in case it should be reopened.
Thanks

Issue History

Date Modified Username Field Change
2023-06-23 15:01 MagasB New Issue
2023-07-07 22:17 gabrieljenik Status new => acknowledged
2023-07-07 22:17 gabrieljenik Note Added: 75983
2023-07-07 22:17 gabrieljenik Bug heat 0 => 2
2023-07-14 15:58 gabrieljenik Note Added: 76089
2023-07-14 15:59 gabrieljenik Status acknowledged => feedback
2023-07-25 01:00 gabrieljenik Note Added: 76254
2023-08-10 13:58 gabrieljenik Status feedback => confirmed
2023-09-13 15:52 gabrieljenik Status confirmed => feedback
2023-10-23 20:42 gabrieljenik Assigned To => gabrieljenik
2023-10-23 20:42 gabrieljenik Status feedback => closed
2023-10-23 20:42 gabrieljenik Resolution open => unable to reproduce
2023-10-23 20:42 gabrieljenik Note Added: 77894
2024-05-12 11:21 khfischbach Issue Monitored: khfischbach
2024-05-12 11:21 khfischbach Bug heat 2 => 4
2024-05-12 11:27 khfischbach Bug heat 4 => 10
2024-07-06 16:05 lavamind Bug heat 10 => 16