Forum Discussion
How can I use Storyline 360 variables in custom xAPI statements as Number (not as String)
Hi,
Perhaps somebody knows this and I miss something obvious :-)
I have a few Storyline360 Number variables.
I am modifying the variable with a Web Object (a little game).
In the end, story...
Hi Everyone,
I have some exciting news to share! We just released another update for Storyline 360. In Update 82, we’ve included important fixes and new features.
One of the fixes we’ve included is:
You no longer need to add quotes to variable values in custom xAPI statements.
To take advantage of this update, launch the Articulate 360 desktop app on your computer and click the Update button next to Storyline 360. You'll find our step-by-step instructions here.
Please let me know if you need additional help!
We are also having this issue. Following and asking for a fix from Articulate.
Hi Shawn,
Sorry to hear that you ran into a similar issue.
We are currently tracking a known bug that causes Storyline to only accept values of variables if they are inside a String (quoted), instead of a number for courses published in xAPI. We've identified that manually removing the quotation marks (") (and related escape characters) in the published export (html5/data/js/xxxxxx.js) resolves the issue. If you have any questions or clarifications regarding the status of the bug or its workaround, you can open a case with our support team here.
Manually removing quotation marks in published content ? I am very sorry, but thats not what users expect ! So Storyline doesnot publish xApi thats the conclusion.
