View Issue Details

IDProjectCategoryView StatusLast Update
12266Feature requestsConditionspublic2017-04-11 15:34
Reporterbrammeleman Assigned To 
Status newResolutionopen 
Summary12266: Condition incorrectly parsed when using more than two possible values for a token attribute
DescriptionIt's not possible to have a condition that consists of more than two values of a token.

For example. A condition that is displayed like this in the condition designer:

First name [Inexistant token table] equals john
First name [Inexistant token table] equals alice
First name [Inexistant token table] equals bob

Will be written as:

((TOKEN:FIRSTNAME == "alice" or TOKEN:FIRSTNAME == "bob") and (TOKEN:FIRSTNAME == "john"))

Obviously, this will never evaluate to True.
Additional InformationThis bug is introduced in Version 2.50+ Build 160725, see also
The uploaded lss file includes the string ((TOKEN:FIRSTNAME == "alice" or TOKEN:FIRSTNAME == "bob") and (TOKEN:FIRSTNAME == "john")), but will show the correct condition in the condition designer.
TagsNo tags attached.




2017-04-11 15:34


Issue History

Date Modified Username Field Change
2017-04-11 15:34 brammeleman New Issue
2017-04-11 15:34 brammeleman File Added: limesurvey_token-condition.lss