urn:scormdriver

Hello, 

I know this was a while ago but hoping someone can assist. My LMS is reporting quiz response data as the following:  urn:scormdriver:Maker[,]urn:scormdriver:Endorsement[,]urn:scormdriver:Signature[,]urn:scormdriver:MICR[,]urn:scormdriver:Foreign[,]urn:scormdriver:LAR[,]urn:scormdriver:CAR[,]urn:scormdriver:Payee[,]urn:scormdriver:Date Correct 0 

The file was uploaded as SCORM 2004 2nd edition. Does this need to be 3rd or 4th edition? 

Thanks, Tracy. I appreciate you chiming in to share what you are experiencing with your Rise 360 content.

This change was part of an update: SCORM messages now prepend urn:scormdriver to the appropriate messages. This results in a behavior change to SCORM reporting logs but not reporting data itself. This change is required and ensures the messages being sent to the LMS are meeting SCORM requirements. 

However, it is still an open issue we are investigating, specific to Rise 360. I have attached this conversation so that we can continue monitoring users impacted and share updates with you.

Hey! I realize this post is a bit old however I'm still having this issue but with Rise. Can you help me with that? I've tried 2004 4th and 3rd edition.

Hello everyone!

Great news!  We just released another update for Articulate 360, and included a few important fixes that you'll see in the release notes here. 

The item you'll be interested in is:

Fixed: We fixed some LMS reporting issues, including multiple-choice responses that appeared in SCORM 2004 reports with a prefix of urn:scormdriver

Just launch the Articulate 360 desktop app on your computer and click the Update button for Storyline 360. Details here.

Please let us know if you have any questions, either here or by reaching out to our Support Engineers directly.

Hi Anna, 

After some additional testing, it looks like we came across a recent bug where:

Response to a Multiple Choice quiz slide includes 'urn:scormdriver' when viewing the report for SCORM 2004 (3rd and 4th) Edition.

We're actively working on a fix, but in the meantime, feel free to roll back to update 38. We'll pop back in here when we have progress to share on it.

Hi There,

I'm having the same issue and i can say we've always used SCORM 2004 and never had this problem until the latest update currently running 3.40. We did a very deep troubleshooting and noticed this issue doesn't happen with versions before 3.38, which is where the problems start. We tested with 3.34 and 3.37 and all good. 

Do we need to roll back the two 3.40 versions we have?

Hi Diana,

Thanks for reaching out! Did you recently switch to SCORM 2004? If so, this may be expected behavior that has been around for a few years. In SCORM 2004 only, the identifiers will be turned into percent-encoded URNs. You can read more about that here:

• SCORM Driver Updated To Version 6.0

If this isn't what you're referring to, feel free to connect with a support engineer, and they can take a closer look at your reportings.