exporting variables to be read in a Google docs spreadsheet
Dec 06, 2012
I've seen Tom's helpful screencast on how to embed a Google docs form into a Storyline project. However, what I want to do is a little different. I'd like to be able to export the values of about a dozen variables from Storyline so I could see them in a spreadsheet the way I would if students entered those values into a Google docs form.
I've got a grammar assessment, and I want to export a student's name and either OK/NEED TO REVIEW/MIGHT WANT TO REVIEW for each of a dozen or so topics. Now, I could just use a final page screen in Storyline showing a student her status on these dozen topics and ask her to fill out an embedded Google docs form in which she basically copies the results manually. These are just initial assessment scores, and I'm not worried about honesty issues. However, this seems like a pretty klutzy way to do things. Would anyone be able to help me out with a suggestion for a better method? I don't know any JavaScript, and my familiarity with Storyline is fairly low.
Thanks!
Dorothy
142 Replies
Thanks Jason - it's always good to have more and newer examples so I appreciate you sharing.
Hi,
I'm trying to do the same thing - EXACTLY! Do you have the scripts? Would be really appreciated. Cheers.
Anthony
Hey John - This thread is a bit dated and if you do not hear back from Kevin soon, you are welcome to reach out to him directly via the 'Contact Me' option on his user profile.
Hello, thank you for your work and generosity Michael and Andrzej. Your tips, tricks and codes are so usefull !
Glad that this thread was able to assist you as well Benoit :)
Hi Tracy,
I've followed your instructions step by step. But somehow it won't work with me.
For this story module I used Storyline 360 and Google Chrome as browser.
Could you please help me with this? I've attached the storyline file and a screenshot of how the js is triggered.
Hi,
Is there any code which can store storyline 360 variables like score in excel sheet? Let me know if anyone has done this before.
Thanks!
Please can you share the demo? and the java script code that will read all the variables and fire the data off. I want to store the result (choice1, choice2, or chioce3) for each of the questions.. exactly what you made, So it'll be of a great help!
Hi Everyone, Just a quick update based on Tracy Trish instruction via this blog post:
http://www.tracyparish.ca/2015/08/how-to-send-variables-from-storyline-to-google-docs.html
The latest script version to include in the story.html is:
<script src=“// http://ajax.googleapis.com/ajax/libs/jquery/1.12.4/jquery.min.js”></script>
I am totally new to html. Can you tell me how to include the latest script version in he story.html?
Thanks
I've been using this method now without fail. Just this past fall used it. I can't remember all the details of my own post that is linked above, but Matthew's method works. Let me know if you have trouble.
https://www.youtube.com/watch?v=5V2pvtFGeyY
Thanks for the reply.
I follow every step in the instruction but still cannot get the variables
posted to the Google Sheet.
Please advise
Regards
KH Wee
Dear Tracy,
I added http to script.src, script.src = '
http://code.jquery.com/jquery-1.11.0.min.js'; suggested by Kumar in the
discussion forum.
It works as I could see the variables are posted in the google sheet.
Thank you & best regards
KH Wee
Tracy's links are no longer valid so I'm trying to cobble things together using the YouTube video she links to above. Is there a new "script.src" link we should be using?
I got it to work! Here's the first JavaScript that needs to be executed at the beginning of the Storyline file:
Awesome Sherri! Happy you got this to work, and so kind of you to come back and share it with the community!
This video by Dmitry M explains another way to export variables from Storyline to Google Sheets. His method requires executing only one JavaScript file: https://youtu.be/g8_Ns6k-K8k
It seems this video isn't available anymore :/
I'm sorry it's gone, Muhammod! I checked and couldn't find it, either. That's really sad because I thought it was an even better solution since it only required one JavaScript file.