The score reported from the articulate tests we've created in my company is sometimes of 0 in our LMS when in fact the final score should've been positive. (at least another value)
I've recently analyzed the logs of the data exported by Articulate Storyline and it seems some of the answers are picked up as "undefined", I am quite sure the issue is comming from the scorm 1.2 content.
Do you have any idea on what could cause this issue ? Does it has to do with the way we've built the test ?
I've seen the "undefined" appear when using a special character or symbol in part of the answer. Does that match the set up of your courses? What version of Storyline are you using?
After further investigation it seems the issue is not comming from the undefined status but from a invalid score in the scorm content.
Some users are returning a score of 0 to our LMS instead of the actual value.
When a new attempt is taken by clicking on the restart button within the course itself, the intScore is getting a value over 100.
It is set in the scorm files that if this value is over 100, it should be reseted to 0, therefore sending a result of 0 to the LMS even when the first attempt was of another value between 1 and 100.
In SetErrorInfo - Num=3 Desc=Invalid Score passed to SetScore (must be between 0-100), intScore=150
This is recurrent for a lot of our LMS content and blocking all new publishing as we cannot track accurately the score of our end users.
Is there a way to have a workaround without republishing all of our content which could take months ?
I can see that you’re still struggling with LMS reporting since you reached out here, in this other discussion, and in case #01164913 . We’d love to help. Can you take a look at the questions I asked in the other discussion? We can keep the conversation going over there!
3 Replies
Hi Morgan,
I've seen the "undefined" appear when using a special character or symbol in part of the answer. Does that match the set up of your courses? What version of Storyline are you using?
Hi,
Thank you for your answer.
After further investigation it seems the issue is not comming from the undefined status but from a invalid score in the scorm content.
Some users are returning a score of 0 to our LMS instead of the actual value.
When a new attempt is taken by clicking on the restart button within the course itself, the intScore is getting a value over 100.
It is set in the scorm files that if this value is over 100, it should be reseted to 0, therefore sending a result of 0 to the LMS even when the first attempt was of another value between 1 and 100.
In SetErrorInfo - Num=3 Desc=Invalid Score passed to SetScore (must be between 0-100), intScore=150This is recurrent for a lot of our LMS content and blocking all new publishing as we cannot track accurately the score of our end users.
Is there a way to have a workaround without republishing all of our content which could take months ?
Thank you,
Morgan
Hi Morgan,
I can see that you’re still struggling with LMS reporting since you reached out here, in this other discussion, and in case #01164913 . We’d love to help. Can you take a look at the questions I asked in the other discussion? We can keep the conversation going over there!
This discussion is closed. You can start a new discussion or contact Articulate Support.