Please help us help you and fill where relevant:
Your LimeSurvey version: Version 3.18.0+190923
Own server or LimeSurvey hosting: CentOS
Survey theme/template: fruity
==================

Howdy fine lime survey folks!

We have surveys using closed access mode with tokens based persistance  with a relevance equation on each survey group to screen out participants who fail to correctly answer theer correct date of birth stored as a token attribute.

QDateofBirth.NAOK == TOKEN:ATTRIBUTE_2

If a participant completes the survey in one session, everything works fine. If the participant leaves the survey and returns using their token at any point before QDateofBirth, they are able to proceed to QDateofBirth and finish the survey normally (within a single session).

However, when a participant leaves the survey after having answered the QDateofBirth question, and returns to finish later using their survey link (with token), the relevancy equation fails, sending them to the end screen.

I am able to display the value {QDateofBirth} in the end screen to verify the value was saved.

Does anyone have an ideas about why this relevance equation would fail upon returning to the survey?

Try screening out with a quota instead of relevance.

Thanks for your response.

How would I go about creating a quota that compares a question response to a value stored in a token attribute?

I have only a basic understanding of using quotas. I am not seeing a way to do this.

A basic example where, for example, we set a quota of 0, comparing a question with code Q1 to TOKEN:ATTRIBUTE_1...

1) Add a hidden (via CSS class) equation type question, code "screenout", with this as a value:




2) Add a quota with a limit of 0 based on "screenout".



Sample survey attached: 

Add a hidden (via CSS class) equation

As this is an equation and it is not used via Javascript, shouldn't it also be possible to hide it via "always hide this question"?

As this is an equation and it is not used via Javascript, shouldn't it also be possible to hide it via "always hide this question"?

I prefer hiding these questions with CSS to ease testing/debugging.

I prefer hiding these questions with CSS to ease testing/debugging.

Understood. I prefer it the other way round though.

I prefer to hide everything that can be hidden via GUI via GUI, as it won't even appear in the source code (some participants can be sneaky...).

Just wanted to make sure that there is technical reason not to use the GUI.

Thanks for all the responses. I'm always impressed with this community.

After reworking the logic to use a quota instead of relevance equations, I figured out that the date format comparison in my relevancy equation was failing due to a difference in date format between the same session, and then upon returning to the survey later.

For example, when I display the input question's date format during the session with {QDateofBirth}, it shows like: 2006-01-01. However, when returning to the survey at a later time, the question's value is retrieved and displayed in the format: 2006-01-01 00:00. 

So ultimately my solution came down to using the strtotime function to format both the question response and the token value to make sure they are the same format like:
{if(date("Y-m-d", strtotime(QDateofBirth)) == date("Y-m-d", strtotime(TOKEN:ATTRIBUTE_2)),"True", "False")}

joeschwab wrote:

For example, when I display the input question's date format during the session with {QDateofBirth}, it shows like: 2006-01-01. However, when returning to the survey at a later time, the question's value is retrieved and displayed in the format: 2006-01-01 00:00.
 

When reading this I would call this a bug.  Or is there a different way to see it?
 

Yeah, it should be consistent regardless of when viewed.

Joe, can you please file a bug report giving full details of use-case, environment, etc?

- bugs.limesurvey.org/

Sure. Although im using an older version (Version 3.18.0+190923). Its possibly not an issue on newer versions?

Can you test a survey at on the demo site?

- demo.limesurvey.org/index.php?r=admin/