SCORM 1.2 Question Text

Feb 25, 2016

I've noticed that our LMS, (SABA) has a field cmi.interactions.n.text that accepts the question text of a slide. Is there any way we can get Storyline2 report the question text to the LMS in this field?



25 Replies
Dave Cox

I have tried both SCORM 1.2 and SCORM 2004 with the same result. I have a captivate module that reports the question text just fine. 

I can send an example of the Scorm logs in the morning. You should be able to duplicate this with any question slide.

I think that this may be a question for your Scorm protocol expert. 


Phil Mayor

Hi Dave

In scorm 1.2 Articulate does not send the question text.  IN Scorm 2004 it does send the question text

I have  seen the question text appear in Kallidus LMS, but have never used scorm 2004 in SABA to test this.

Dave Cox

Thank you Phil. You are correct, SCORM 2004 does send the question. I didn't see when when I tried it before becuase I was looking for the wrong parameter. SCORM 2004 puts the value in CMI.interactions.n.description. I was expecting it in CMI.interactions.n.text, which is where Captivate appears to put it.

Thanks for the help with that.

Brian Allen

This is very helpful to know... Seems like every LMS stores SCORM interaction data differently.

After your post I had started looking at some of ours in our SumTotal LMS and had noticed that it looked like we had question text for 2004 but none for 1.2, so I thought there was something to it...

Matt Mayer

Hello Dave,

We also use Saba and have the same issue. It is a SCORM 2004 vs SCORM 1.2 articulate issue. It has nothing to do with Saba. I have had Saba IT pull the files apart and there is no field for.text or .descrption in a SCORM 1.2 quiz published from STORYLINE nor Quizmaker '13.

Did you say that Captivate enables these fields in a SCORM 1.2 Quiz?

We are publishing course for Mobile, and SCORM 1.2 is only available on Mobile, however we need this data set, so we are not able to publish such quizzes for mobile at this time.

Dave Cox

I discovered that SCORM_2004 wouldn't work with SABA. I couldn't get it to report any scores at all. We reverted bact to SCORM 1.2. 

To solve the problem, I patched the SCORMFunctions.js to send the required text to SABA. Since SABA looks for the question in a text field, I'm sending the information to the value text instead of description. I've updated all of our courses with this patch, and it has been working fine since.

This file is in your packages lms folder.

I added this code after the line: "//ignore the description parameter in SCORM 1.2, there is nothing we can do with it"

if (strDescription != undefined && strDescription != null && strDescription != ""){

blnResult = SCORM_CallLMSSetValue("cmi.interactions." + intInteractionIndex + ".text", strDescription) && blnResult;


I'm attaching a copy of the patched file for you here.

I hope that this helps,


Dustin Bauman


Thank you very much. After working on this for a good while, thinking maybe it had something to do with the stacking order in SL, I found this article. After seeing that the interactions.X.text field was blank and seeing that you had figured this out, I tested and it works perfectly. Thank you very much for sharing this.

Lauri Hagan

I tried the SCORMFunctions.js patch above that Dave posted but it did not work for me.  Previously I was using the replacement files that Vance Sumner had posted on the Saba Community site and they worked perfectly until today when I updated Storyline 360 to current version. Does anyone else have new patch or replacement files to get the question text to appear in Saba LMS when publishing to SCORM 1.2? SCORM 2004 does not work for us for the reasons cited above.

Dave Cox

Hi Lauri,

A lot has changed in Storyline 360  since Storyline 2, and I haven't looked at that patch since Storyline 2. The problem stems from the fact that the SCORM 1.2 spec does not specify what to do with the question text, and therefore is was not implemented in Storyline.

I will look at it as soon as I can, to see if I can rewrite the patch for you. I'm currently in the middle of a move, so it may be a bit. I apologize for the inconveniance.


Dustin Bauman

I can post the working patch for SL360, I have kept them up to date as we are using Saba as well. The big thing is that SL changed from SCORMFunctions.js to SCORMDriver.js, that is probably one of the reasons it is no longer working.

Let me know if you would like the new files and where this needs to be placed and I will gladly upload. We have been successfully using q level reporting for over 2 years now with Saba.

FYI, I worked with Vance and Dave's patch to get the Saba patch you have from Vance to work in Saba.

Lauri Hagan

Yes! It would be great if you could post the files and the Articulate 360 folders they belong in. Thank you!

Please note that this e-mail and any files transmitted from
Memorial Sloan Kettering Cancer Center may be privileged, confidential,
and protected from disclosure under applicable law. If the reader of
this message is not the intended recipient, or an employee or agent
responsible for delivering this message to the intended recipient,
you are hereby notified that any reading, dissemination, distribution,
copying, or other use of this communication or any of its attachments
is strictly prohibited. If you have received this communication in
error, please notify the sender immediately by replying to this message
and deleting this message, any attachments, and all copies and backups
from your computer.

Jarid Goodwill

Hi, Dustin. I recently tried to implement Dave's solution on a SCORM 1.2 course and noticed the absence of the SCORMFunctions file. Would you mind sharing a sample SCORMDriver file and note where the changes were made in the code?

I know this is an old thread but having your solution would really help right now.

Ian Janes

I'll just share this in the hope that it helps anyone who also stumbles across this thread and may not be aware: the cmi.interactions.n.text field is not part of the SCORM spec (either 1.2 or 2004; cmi.interactions.n.description is 2004-only), so in that sense this absolutely was a SABA issue rather than a SCORM or Storyline issue.