Please provide a brief description.
Please make a selection.
Please make a selection.
Please provide a description.
@jfass
Account
Account
Writing Data to the Same Row in Google Sheets
Currently, each time data is written to Google Sheets, it is written to a new row. Is there a way to have the data written twice to the same row IF the data is coming from 2 different Storyline Files.
Here is the use case...
A user completes a pre-learning questionnaire and data is written to Row 1 in Columns A and B
A user then completes a post-learning questionnaire and data is written to Row 1 Column C
That way, when I review the data, a see all the data for a single user on one row in columns A, B, and C.
Here is the use case...
A user completes a pre-learning questionnaire and data is written to Row 1 in Columns A and B
A user then completes a post-learning questionnaire and data is written to Row 1 Column C
That way, when I review the data, a see all the data for a single user on one row in columns A, B, and C.
Reply
Posted on 11/9/2025
@support
The number of the working row is saved to the stencilsheetstoken variable in Storyline, so if you change this variable before you send the post-learning data, then you'll write to the row you need.
If you're comfortable with JavaScript, it should be quite easy for you to implement. For example, if you drop a cookie with the row number when the variable stencilsheetstoken changes in the first storyline file. Then, in the second file, read the cookie value and save it to stencilsheetstoken. Just note that you want to set the cookie to persist across sessions and give it a long expiration time.
A less technical approach would be to tell the learner "Here's your unique ID, write it down for later." and then ask for this number in the second Storyline file. The issue with this, though, is that they might enter someone else's number. You can mitigate it by maybe reading a certain field from that row first (maybe their email or last name) and if it doesn't match either what the LMS says or what they enter - ask to re-enter.
Another option could work well if you're good with formulas. You can come up with a formula to find the user's row by email or last name, write the formula to the sheet with SheetsSet(), then read the calculated value with SheetsGet() and save that value into stencilsheetstoken.
The point is, you can certainly set the row number manually, how you do it depends on the setup and your technical expertise.
If you're comfortable with JavaScript, it should be quite easy for you to implement. For example, if you drop a cookie with the row number when the variable stencilsheetstoken changes in the first storyline file. Then, in the second file, read the cookie value and save it to stencilsheetstoken. Just note that you want to set the cookie to persist across sessions and give it a long expiration time.
A less technical approach would be to tell the learner "Here's your unique ID, write it down for later." and then ask for this number in the second Storyline file. The issue with this, though, is that they might enter someone else's number. You can mitigate it by maybe reading a certain field from that row first (maybe their email or last name) and if it doesn't match either what the LMS says or what they enter - ask to re-enter.
Another option could work well if you're good with formulas. You can come up with a formula to find the user's row by email or last name, write the formula to the sheet with SheetsSet(), then read the calculated value with SheetsGet() and save that value into stencilsheetstoken.
The point is, you can certainly set the row number manually, how you do it depends on the setup and your technical expertise.
Reply
Posted on 11/9/2025