I set up a new attribute for my token fields. The field either says "yes" or "no" and is a constant.

For a group of questions, I created a relevance: ((TOKEN:ATTRIBUTE_1 == "yes"))
The group of questions are not showing up for any of the tokens, including the ones that have the attribute "yes". I understand this may be case sensitive and both are lower case.

I also created relevance for individual questions. That didn't work either. When I deleted the relevance and tried to re-create it for the individual questions, the "token" tab is greyed out and I cannot re-create it.

Any ideas??

EDIT: I see another post that this may be an issue with 2.05. This is a new survey created in Version 2.05+ Build 141020

Thanks,
Alex

Well, this here is not a condition but a relevance equation, or am I wrong?

Why do you open and close two "((" ?

How does your question page look like? Is the relevance equation highlighted somehow?

You're totally right it's relevance not condition.

I copied that from what it originally created when I was able to get it to make the condition based on my selections. I'll give it a try without the double (())

tried it without the double (()) and it's still a no-go. Doesn't show the question group for tokens with attribute_1 == "yes"

Below is a screen shot of the greyed out token tab.

Seems like LS doesn't recognise that there are token fields. Did you create tokens and attributes?

Yep. Created tokens to test with attributes to test it, and that's when I found it wasn't showing those questions. I went back to edit the relevance and that's when it started acting funny and not letting me edit the token tab of the relevance screen.

Does it work if you enter the condition directly into the Relevance field instead of using the conditions designer tool?

I tried deleting all of them through the conditions designer tool, and then I manually entered it into the relevance field. Still does not work. With a relevance (TOKEN:ATTRIBUTE_1 == "yes") the question never shows up, whether or not "yes" is in the token attribute_1 field.

Your survey is NOT ANONYMOUS ?

If not : you can not use TOKEN attribute

It is an anonymous survey.

Well that explains it then. As Denis says, you have no access to token data in anonymous surveys.