Tokens in Cases and Survey Results

Asked by Andrew Tokmakoff on 2016-02-15


I am trying to do some data extraction from a Quexs 1.14.0 install. I am having trouble connecting the Quexs admin data (in the tables cases, calls, etc.) with the actual limesurvey data which has been collected for those cases. When I try to export thge data from Limesurvey, adding the Quexs case outcome and sample variables as csv, I get empty columns, but I do get a token (a clean integer)..

My survey is dual language (en and pt).

When I look into the cases table, I see that there is a generated hex token which is not the same as the pure integer token I am seeing in the data extract, and in the survey results table itself. When I look into the survey tokens table, I see that both the integer token and the hex token are in there, typically right after each other in sequential rows.

Is anyone able to tell me if this is expected behaviour? I would have expected the case hex token to have been used consistently throughout the tables, providing a reference to the survey result row in the survey results table..? Currently I am unable to tie the case to the associated results as these tokens are different and there seems to be no way to resolve the two tokens.

Thanks in advance for your help,


Question information

English Edit question
queXS Edit question
No assignee Edit question
Last query:
Last reply:
Adam Zammit (adamzammit) said : #1

Hi Andrew,

I have not seen this problem before. This is not expected behaviour. The "token" in the limesurvey databases (token and survey tables) should match the token in the queXS case table.

It sounds like a bug - I would need more information to assist. Are you able to send me (privately) a complete dump of your queXS database to review?

Adam Zammit

Andrew Tokmakoff (tokmakoff-q) said : #2

Hi Adam,

Yes, I can send you a db dump. I will send it to your account in a moment.



Launchpad Janitor (janitor) said : #3

This question was expired because it remained in the 'Open' state without activity for the last 15 days.

Adam Zammit (adamzammit) said : #4

A note: The issue here was when creating a questionnaire - the same instrument was selected as both the main instrument AND the respondent selection instrument. Resolved by creating a new questionnaire in queXS and selecting "Basic respondent selection" for the respondent selection option.

Adam Zammit (adamzammit) said : #5

Added reasons

Can you help with this problem?

Provide an answer of your own, or ask Andrew Tokmakoff for more information if necessary.

To post a message you must log in.