Variable not saving to LMS properly
Jul 11, 2017
Hello all,
I've came across a problem I can't handle with my knowledge.
I have a course with 7 interactions, on which, depends on answers, I give points form 0 to 1, like 0.15, or 0.5.
It is done on feedback layers, where I simply have trigger "Add 0.5 to variable points" or "Add 0.2 when ... smth happens". Because I have very individual interactions, if someones wonder why it is not handled like default way.
Then, it is calculated on Master Slide Layer as follows:
Set calc equal to the value of points when variable points change
Divide calc by 7 when variable points change
Multiply calc by 100 when variable points change
Set percent equal to calc when calc changes
etc. etc.,
I show on the layer all the variables, so I have something like points - calc - percent. I finish intercation, I got 0.8 - 11.2 - 11. All the values are ok.
Now I shut down the course and enter it once again.
And I see 0 - 11.2 - 11, so the calc and percent are stored normally, and points are reseted to 0 (I don't reset points anywhere) - why is it happening?
It's scorm 1.2 and suspestion data are not so long, 237 characters.
Any idea here? Or how I can fix it?
11 Replies
I've enabled SCORM debug.
The suspend data send and received by LMS is identical.
So it seems that storyline/scorm part doesn't write the value of my points variable, even when it has added and added some values there. Why so?
And third clue - I've made a blank lesson which 5 slides.
1 - add 0.2 to points
2 - nothing
3 - add 0.2 to points
4 - nothing
5 - add 0.2 to points, and it is last slide, so the completion status is set.
I quit the scorm, and reenter it. It prompts me if I want to continue from the last place. I say yes, I'm on 5th slide in review mode, and the points variable is... 0.2.
Why it is 0.2?! Why not 0, so it would some kind of bug, or 0.6, so it would mean that something with my course is wrong. Or why not 0.4, so it would mean, that only the last slide didn't save the score.
0.2 is so... irrational.
Hi Mateusz,
With variables it's often something as simple as trigger order or how it was set up - but those are things that folks would need to see the .story file to check.
If you want to share it here (even your sample file) by using the "add attachment" button then others in the community can take a look.
Here you go.
You can publish it to scorm 1.2 and upload to scormcloud, open, move to the last slide, close, and reopen. The two variables will be 0 instead of 0.6.
Thanks Mateusz - I'm taking a look!
Hi Mateusz,
Thanks for your patience while I tested this file.
First, I wanted to note that there was nothing in the file to report your variable values to an LMS. Variable values are not automatically reported to the LMS, unless the exist in a question type (fill in the blank, short answer, etc.) so some users have looked at this method to report the value of a variable to an LMS.
Next, I saw that the variables are set correctly the first time through, but upon closing and resuming the course that the value is reset to zero. I tested on a new file as well, and saw the same thing and was able to determine that for the variables you were using (a numeric value with decimal places) the triggers of the slide you resume on are the only ones taking effect and the values are reset. So for example, if you had resumed on slide 5 the value would be 0.2 as there is a trigger at the start of the timeline to set it as such.
This issue only occurred with decimals - so I'll report it to our team as a possible software bug. In the meantime you could use whole numbers and those will track correctly on the slide even with a resume.
Hello Ashley and thanks for your reply.
First, I wanted to note that there was nothing in the file to report your variable values to an LMS. Variable values are not automatically reported to the LMS, unless the exist in a question type (fill in the blank, short answer, etc.) so some users have looked at this method to report the value of a variable to an LMS.
That's irrelevant in this case, it's just the test file :) I know how to report to the LMS :)
This issue only occurred with decimals - so I'll report it to our team as a possible software bug. In the meantime you could use whole numbers and those will track correctly on the slide even with a resume.
And that's the problem - I've checked reporting both floats and integers once again. Integers save properly with "add" function. So that's good.
Now, I've made another test file and on slides we have triggers like:
1 - add 1.33 to points
2 -
3 - add 1.33 to points
4 -
5 - add 1.33 to points
6 -
I go through slide 1,2,3,4 so my 'points' variable should be 2.66. When I relaunch, it is 2. So, the decimals are not saved in course progress.
I assume that somewhere in storyline .js files variables are converted to integers when saving, instead of staying floats.
Seems like bug that is pretty easily to fix. I could probably even fix it myself, but I don't have time to dig inside the storyline files.
Ashley, however small, it seems like a major bug to the software. You are giving oppurtunity to save decimals, but they are converted to integer numbers. Could you please pass that thing to the developers and came with some update in really short time? SL2 is out for two years. And now, another sad thing - I've checked with storyline 3 and it has the same bug :(
Have a nice day
Hi Mateusz,
That's irrelevant in this case, it's just the test file :) I know how to report to the LMS :)
Always have to check, just in case!
I saw the same issue in Storyline 3 and 360 - so I did report it across all versions to our team. I know it's a big issue for you, and all of that information helps drive the priority for fixes.
Depending on priority and risk, some bugs can be fixed quickly, while others take longer to resolve. Here's more information on how we identify and tackle bugs.
I'll keep you posted here once there is some more information to share!
Hi Mateusz,
I have checked the file, and was able to replicate the issue.
Instead of increment the value if we set the value then it is working fine.
It looks strange but it is working.
I also faced the same issue when saving the variables on the LMS.
Developed something very dynamic using JavaScript and when it come for saving data everything went for toss :(
Hi Mateusz and Shailesh,
I have some good news to share!
We just released the newest version of Storyline 360 (Build 3.36.21213.0) this morning, which fixed adjusted number variables with decimal values being reset to their default values when resuming a course.
The next step is to update Storyline 360 by heading to your Articulate 360 desktop app and clicking "Update" next to Storyline 360.
As always, we are happy to answer any questions you have by posting in this discussion, or you can contact our Support Engineers directly here.
That's great news!!
Thanks Vincent for the update..that will help a lot
This discussion is closed. You can start a new discussion or contact Articulate Support.