Forum Discussion
Storyline xAPI reporting issues with imported slides
One of our users imported Powerpoint slides and it seems that that has stripped away the capability for xAPI statements to be sent to the LRS system. The reporting shows no messages come through even when the xAPI triggers are entered directly to the slides. Does importing slides from powerpoint strip the xAPI reporting capability from the package, and if so is there any way to repair the package instead of recreating the entire course? All other xAPI packages created from scratch or templates report fine.
We found the problem. The name of the course was long and for some reason Storyline made the variable "TC_Course_Name" into 2 lines in the scormdriver.js file upon publish. Our player wasn't picking up the course name since that was errored out so no xAPI statements. Support is looking into it.
4 Replies
Short answer: no — importing PowerPoint slides doesn't strip xAPI capability from a package. The statements come from the player and the publish settings, not from where a slide originated, so an imported slide can fire xAPI triggers just like a native one.
Since your other packages report fine, I'd check the publish side of this file first:
1. Confirm this .story was published with xAPI selected and the correct LRS endpoint. It's easy for a file built from an import to get republished from an older copy with different reporting settings.
2. Check Reporting and Tracking. If the course tracks by quiz result and the imported deck has no result slide, no completion statement will fire. If it tracks by slides viewed, make sure the imported slides are in the tracked set.
3. Test with the LRS statement viewer open and see whether any statements arrive at all. Nothing at all points at the endpoint or the launch; statements arriving but no completion points at the tracking setting.
If all of that checks out, look at the triggers themselves — confirm the "Send xAPI statement" triggers sit on the actual slides and that the actor, verb and object are filled in. One of those usually turns out to be the culprit, and none of them means rebuilding the course.
Hi, dclohman!
I'm glad ronald-hicks has stepped in to help out! If you need further assistance, please don't hesitate to follow up here or privately in a support case.
We found the problem. The name of the course was long and for some reason Storyline made the variable "TC_Course_Name" into 2 lines in the scormdriver.js file upon publish. Our player wasn't picking up the course name since that was errored out so no xAPI statements. Support is looking into it.
Thank you for the response!
