I'm trying to use xAPI in Storyline 360 to send the number of correct questions to the Watershed LRS. I have a variable in storyline that I named "correct_questions" and when I take the course and that variable is = to 10 I push a button with a trigger to send xAPI statement with the result being the my variable.
I look in Watershed LRS and I see that my random number user answered 10. Great
Now I reopen the course and make the variable 12 and push my send button, but when I look in the LRS is shows that my new random number user answered 12, but so does the old one. what am I doing wrong?
Hello Bernard. Did you ever get more information on this issue. I am working with a client where we are experiencing some inexplicable data results that may involve holding on to the values of variables from previous slides.
From what I understood from Bernard's inquiry, it looks their course is reporting two values to their LMS. Can I ask if you are encountering the same behavior? If so, did you follow the steps in this article to send the value of a variable to an LMS as an xAPI statement?
One troubleshooting step that you can do is to test your course in SCORM Cloud so you can see what data will be recorded in the reporting section. If you are able to replicate the behavior in SCORM Cloud, would you be willing to share a copy of your project file here or in private by opening a support case so we can take a closer look at what's happening? We'll delete it when we're done testing!
Sorry for the delayed response. I missed that you had responded. The issue is that we are using a variable to store the answer text in a MC question. We are then sending that variable in an xapi statement. However, rather than reporting the data that we input in the xapi statement for a specific slide, it is reporting the data from a much earlier xapi statement.
Also we can NOT recreate this in SCORM.cloud. And in fact, with the initial round of testing using Watershed the data was fine. It was only upon hundreds of learners taking the course that the data had issues.
Let me know if you have any other questions. Would love to get your perspective.
If your course works properly in SCORM Cloud but not in your LMS, there's a chance that the issue might be LMS specific. One troubleshooting step that you can do is to enable the LMS debug logs for your course and then replicate the issue:
4 Replies
Hello Bernard. Did you ever get more information on this issue. I am working with a client where we are experiencing some inexplicable data results that may involve holding on to the values of variables from previous slides.
Hello Mary-Scott,
Happy to help!
From what I understood from Bernard's inquiry, it looks their course is reporting two values to their LMS. Can I ask if you are encountering the same behavior? If so, did you follow the steps in this article to send the value of a variable to an LMS as an xAPI statement?
One troubleshooting step that you can do is to test your course in SCORM Cloud so you can see what data will be recorded in the reporting section. If you are able to replicate the behavior in SCORM Cloud, would you be willing to share a copy of your project file here or in private by opening a support case so we can take a closer look at what's happening? We'll delete it when we're done testing!
Hello Joe.
Sorry for the delayed response. I missed that you had responded. The issue is that we are using a variable to store the answer text in a MC question. We are then sending that variable in an xapi statement. However, rather than reporting the data that we input in the xapi statement for a specific slide, it is reporting the data from a much earlier xapi statement.
Also we can NOT recreate this in SCORM.cloud. And in fact, with the initial round of testing using Watershed the data was fine. It was only upon hundreds of learners taking the course that the data had issues.
Let me know if you have any other questions. Would love to get your perspective.
Hi Mary-Scott,
Thanks for the additional information!
If your course works properly in SCORM Cloud but not in your LMS, there's a chance that the issue might be LMS specific. One troubleshooting step that you can do is to enable the LMS debug logs for your course and then replicate the issue:
Seeing what your course is communicating in the background might help provide more information on what's happening.