Forum Discussion
Rise Course xAPI File Structure Change??
I'm creating courses in Rise 360 and publishing in xAPI (TinCan). The published xAPI file structure from 3 days ago is completely different to the file structure when republishing the same course today.
In fact the new xAPI file structure contains "SCORM" files??? See images.
12 Replies
The new xAPI file published from Rise 360 is not tracking on our LMS. I've also tested it on SCORM Cloud, which is recognising the file as "xAPI" but it is not tracking correctly on there either.
I am having the same issue today, xAPI scorm file doesn't open in our LMS. Is there some error?
Exactly what we're seeing. File structure being published from Rise is completely different. Must be some error.
I'm having the same trouble. I found there is an indexAPI.html file in the scormdriver folder that works for the basic xAPI stuff. But I used the Mighty plug-in and developed a lot (A LOT) of additional xAPI statements that now are not recognized. This severely hinders the work we were doing. It was working fine yesterday morning and now six courses are stripped of the ability to see what's happening inside the course.
I've raised a Support Ticket for this with Articulate. Don't know how to escalate further it or speak to an actual human.
Our LMS (and SCORM Cloud) is no longer able to track "Progress" of these xAPI files. And they're breaking completely on our Translator Tool.We have the same problem. Have you received a response from Articulate yet?
I received instructions from the support how to make it work. I wander was there any communication previously about the change?
To make sure your export works correctly in your LMS, please see the following PDF for instructions on how to integrate xAPI content into an LMS.
Incorporating a TinCan LRS into an LMSAlso, not sure if it's helpful but I get basic xAPI statements from Rise when I point the LRS to the indexAPI.html path found in the /scormdriver/ folder.
Still haven't received any reply from my Support Ticket submission, but our software reseller chased up and received this from a Customer Support Specilaist:
"We've recently updated the structure of Rise xAPI exports to create a more consistent experience across all LMS types.
Here's what that means:
What changed- All Rise exports (AICC, SCORM, cmi5, and xAPI) now share the same folder structure
- xAPI packages now use our newer, more robust driver technology
- The internal files are organized more consistently
Why we made this change
This update creates a foundation for future improvements and makes it easier for us to enhance LMS functionality going forward. It's not just cleanup—it's preparation for even better features.
Identifying xAPI content
It's simple: if your export package contains a tincan.xml file, it's still xAPI content. The folder names (like "scormcontent") are just standard naming conventions we use across all export types.
If you're experiencing issues
Some LMS systems with custom xAPI implementations may need adjustment. The solution is straightforward:- Ensure your LMS follows standard xAPI specifications
- Configure your LMS to use the tincan.xml file for launching content
For detailed guidance, check out the xAPI guide.
Once your system is configured correctly, your Rise content will work seamlessly—both now and with future updates."
How such a substantial change can be updated and released without letting users know is absolutely mind-blowing. 😡
