View Issue Details

This issue affects 1 person(s).
 4
IDProjectCategoryView StatusLast Update
08499Bug reportsCentral participant databasepublic2014-01-17 13:42
Reporterduvemyster Assigned Toc_schmitz  
PrioritynormalSeverityminor 
Status closedResolutionwon't fix 
Product Version2.00+ 
Summary08499: Unable to associate participants pre-existing in both a token table and the central participant database
Description

When a participant already has both a token table record and a central participant database record, it seems like the intent is to be able to establish an association such that the survey lists in the subgrid. However, this association does not currently seem to be created unless one of the records is first deleted.

Steps To Reproduce

Setup a record in the central database and a record in a token table that have the same name and email address. (In my scenario I also had one pre-mapped attribute, though that might not necessarily matter.) From there, two different approaches reproduce this:

  1. Start from token table > Add participants to the central database > Continue > Results are that no association is created (whether or not the pre-mapped attributes checkbox is checked).

or

  1. Start from central participant database > Add to survey > Continue > Results are that no association is created (whether or not the pre-mapped attributes checkbox is checked).
Additional Information

I was in process of migrating multiple token tables to the central participant database when running into this, so the steps initially first taken were:

  1. Added records from one token table to the central participant database (records added and associations with the survey were record in the central database).
  2. Then attempted to add the same participants from a different token table to the central database, and this time the survey associations were not recorded in the central database.
TagsNo tags attached.
Bug heat4
Complete LimeSurvey version number (& build)Build 131206
I will donate to the project if issue is resolvedNo
BrowserGoogle Chrome Version 31.0.1650.63 m
Database type & versionMySQL 5.1
Server OS (if known)Linux
Webserver software & version (if known)Apache/2.2
PHP Version5.4.10
Git branch / Pull Request URL

Users monitoring this issue

There are no users monitoring this issue.

Activities

duvemyster

duvemyster

2013-12-31 05:34

reporter   ~27705

Related to 08498?

c_schmitz

c_schmitz

2014-01-17 13:42

administrator   ~27949

That is currently the intended behaviour.

Issue History

Date Modified Username Field Change
2013-12-31 05:30 duvemyster New Issue
2013-12-31 05:34 duvemyster Note Added: 27705
2014-01-17 13:40 c_schmitz Relationship added parent of 08498
2014-01-17 13:41 c_schmitz Relationship deleted parent of 08498
2014-01-17 13:42 c_schmitz Note Added: 27949
2014-01-17 13:42 c_schmitz Status new => closed
2014-01-17 13:42 c_schmitz Assigned To => c_schmitz
2014-01-17 13:42 c_schmitz Resolution open => won't fix