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!
Hi Remo! I asked the same question with no response, so I'll file a ticket with support. This is a bug (or by design but than the design is flawed). Raw HAS to be a number. We can't send it as a string, it's non-conformant.
What I'm doing now is after publishing I run a Python script on the published .js files to remove the /" part for the /"variable/" when I DO want this to be a number. They are page-based .js files in html5\data\js\.
