Forum Discussion
Problem with automatically generated xAPI statements in Articulate Storyline
Built-in statements are generated by the player, so if nothing changed in your project, I'd treat this as a publishing-side regression until proven otherwise.
Three things I'd pin down. First, the exact Storyline build behind each export (Help > About) — if the old and new exports came from different builds, that's your prime suspect. Second, the raw statement in your LRS: confirm whether it's the object name/description that changed to the ID, and whether the verbs and extensions are otherwise identical. That tells support exactly where the player started sending the ID. Third, rule out slide titles on your side — the player pulls the statement label from the slide title, so it's worth a sanity check that every slide actually has a title in the Scenes panel. Blank or auto-generated titles are an easy thing to rule out.
If you need it working now rather than waiting on a fix, you can bypass the built-in statements and fire your own via JavaScript with the title hardcoded. Happy to walk you through that if it comes to it.
Thank you very much, ronald-hicks!
I checked into the three things:
1. Articulate build means Articulate version, right? The one with the correctly displayed slide titles stems from version 3.90.32850.0, whereas the new one is version 3.123.37616.0.
2. The statement in the LRS is identical in terms of verb and object ID, the only difference is that the slide title doesn't show in "name" and "description" and these remain empty instead.
3. I haven't touched the slide titles at all, so the slides are still named identically.
So 1. remains the main suspect I guess. Thanks very much for your help and the JavaScript suggestion! I think I will publish the units like this if I can't find a quick solution and will try to reconstruct the slide titles from the slide IDs retrospectively.Regarding 2., here's a screenshot comparing the two raw statements.
Yes — build means exactly that full number (the one under Help > About), and you've got them. That's a big jump: 3.90 to 3.123. When the only delta between two exports is the Storyline build and the statements change, that's almost certainly a change in how the player generates built-in statements. I'd send Articulate support both build numbers plus a minimal .story that reproduces it — that's exactly the kind of regression they can confirm and log.
On the retrospective reconstruction: if you go that route, build the slide-ID-to-title map once per course and keep it alongside your LRS exports. The object IDs are stable within a project, so a lookup table you make today stays valid for that course. Just don't assume the same IDs carry over to a different course.
