Please help us help you and fill where relevant:
Your LimeSurvey version: Version 3.28.5
Own server or LimeSurvey hosting: LimeSurvey
Survey theme/template: extends_vanilla
==================

Our Survey is broken down into 10 Sections/Question Groups, as it covers different areas of business (eg, Environment, HR, etc).
A company may have 2 or 3 different users accessing the Survey to update the section relevant to them.
However, we've had users report that their answers are being erased whenever another user updates a different section of the Survey, eg, if the person filling out the Environment section hits Resume Later, then the person who filled out the HR section loses all the answers they submitted earlier.

Is this the way LimeSurvey works?  I'm sure we've had other companies have multiple users fill out different sections and save/submit them without LS overwriting the field data that other users filled in.
Is this a bug, or is it not possible to have multiple users filling out different sections of the same survey?

BITCNI wrote:

A company may have 2 or 3 different users accessing the Survey to update the section relevant to them.
However, we've had users report that their answers are being erased whenever another user updates a different section of the Survey, eg, if the person filling out the Environment section hits Resume Later, then the person who filled out the HR section loses all the answers they submitted earlier.
 

Did you try to reproduce the issue?  To me this sounds like intended behavior when using the "Resume Later button". I don't think that function is working with multiuseraccess.
If I had to cope with more than one respondent in the same response set, I would try to use token persistence to allow reaccessing the responseset.


 

Yes: we did try to reproduce the issue.  It appeared that if you hit the Resume Later button and then went into your Browser History to return the survey, the Browser said that you had to resubmit the data, and when you hit resubmit, it overwrote the other person's answers with blanks.

This is what we have the Settings set to:

BITCNI wrote:

Yes: we did try to reproduce the issue.  It appeared that if you hit the Resume Later button and then went into your Browser History to return the survey, the Browser said that you had to resubmit the data, and when you hit resubmit, it overwrote the other person's answers with blanks.
 

Ok, that's the confirmation of my thoughts.  You will need to hide/disable the "Resume later function" and need to use only tokens (perhaps you already use them). With the settings you have people can reenter the response-record via token. That way nothing will be overwritten en bloc.
 

Cheers, but we want/need people to be able to do the Survey in parts. It may take months to complete it, as so many departments are involved. If we disable the Resume later function, can people save the record after only filling in a few questions?

I agree with Jelo. You will need to use tokens.

The way that I handle this requirement is:

1) Use tokens.
2) Enable token-based response persistence == ON.
3) Allow multiple responses or update responses with one token == ON.
4) Modify the "Resume later" button text to "Save current answers".

In this case, multiple people can respond to a single token data set until the final submit button is clicked.

Clicking "Save current answers" does not pop up the resume later dialog but does save all answers and reloads the page.

Thanks for your response, Tony, but I don't understand, as we are *already* using tokens?

[1) Use tokens]
We already are

[2) Enable token-based response persistence == ON]
You mean we should turn it to OFF?

[3) Allow multiple responses or update responses with one token == ON]
Again, turn it to OFF?  The wording of this implies that people then CANNOT update responses with one Token.  That's very confusing

[4) Modify the "Resume later" button text to "Save current answers".]
[Is this easy to do, or does it require a plugin in something?  I don't an option for this]

In this case, multiple people can respond to a single token data set until the final submit button is clicked.

Thanks for clarifying the above.

Allow multiple responses (when token-based response persistence is OFF) or update responses with one token (when token-based response persistence is ON).

If someone hits "Resume later" the answers are saved separately and restored back (which means overwriting other modifications) into the responseset.
So preventing anyone to use "Resume later" ensures that nothing gets overwritten without intention.

So, by turning it off, how do people 'Save' the survey when they do have to come back the next day, week, or month to finish it?

If we turn 'Resume Later' off, is there a 'Save' button instead?

BITCNI wrote:

So, by turning it off, how do people 'Save' the survey when they do have to come back the next day, week, or month to finish it?
 

They just use the surveylink with the token. The token is enough to reenter the survey and the response set.
That's what "token-based response persistence" mean.
 

Thank you, but what I meant is that if there is no SAVE button, how do users know their responses have been saved when they close the browser?

This is something you insert in the invitation mail as there already is "Please click the link below to start the survey"
Or you explain it on the welcome page.

Like:
"If you want to stop and continue later, you can close your browser.
Clicking on the provided link again will lead you to the question where you left the survey"

Joffm