Bug? Numeric variables in custom xAPI statements
Oct 21, 2022
Pinned Reply
Hi, AVT Connect and Jurgen!
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!
4 Replies
Hello PJ,
Thank you for opening a support case!
I see you are working with my colleague Cleo, who logged this behavior as a possible software bug where Storyline only accepts the variables if they are inside a String (quoted), instead of a number.
We are investigating the issue, and we will let you know once we have new information to share.
Hope that you have a great day and happy developing!☀️
Thanks, I'm on annual leave for the coming week so won't be picking up emails etc. Looking forward to a fix :)
this is a known problem (since months)
https://community.articulate.com/discussions/articulate-storyline/how-can-i-use-storyline-360-variables-in-custom-xapi-statements-as-number-not-as-string
Hi, AVT Connect and Jurgen!
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!