Forum Discussion
LRS xAPI Data POST
We have our LRS stood up and Articulate Storyline has the connection in the presentation and the connection is being accepted by our LRS.
The issue we are seeing is that it's only sending OPTIONS requests and not sending the POST request for the xAPI actions/engagements we have set in the presentation.
Does anyone know why this would be happening and how to correct it?
The OPTIONS request is returning the 204 as expected so it's not failing, and the presentation looks to be sending the OPTIONS for each of the engagements, but not a POST.
Thank you JoseTansengco ! We were able to figure out the issue. Articulate isn't using a POST here, it's using a PUT. This wasn't added to the allowable OPTIONS, once we change that it works as expected.
Hello ryanHepler,
Happy to test this issue for you!Since this issue involves multiple systems, I'll need to test your course to isolate if the issue is with your LRS, LMS, or how the course was published in Storyline 360. Just to give you an idea of how I'll be doing my testing, I'll upload your course in SCORM Cloud and connect it to either Veracity Learning or Watershed LRS then observe which data is recorded.
Would you be willing to share a copy of your project file here or in private by opening a support case so we can take a closer look at what's happening? We'll delete it when we're done testing!
Awesome, thank you! I'll get it for you and upload!
Here is the Articulate Storyline presentation in question. Thank you.
Thank you JoseTansengco ! We were able to figure out the issue. Articulate isn't using a POST here, it's using a PUT. This wasn't added to the allowable OPTIONS, once we change that it works as expected.
JoseTansengcoTwo question for you. For Rise, it doesn't look like we can put the LRS connection details in the Rise presentation at Export time. How would we add the LRS connection details to the Rise presentation when exporting it in xAPI?
The details that come back in Storyline lack the Canvas course id or other details that will help us make use of the data in the database. Do you know if we can adjust the items that come back in the Storyline and Rise LRS items?Hi ryanHepler!
Happy to jump in here!
Allow me to address each of your questions individually:
- That behavior is expected, as currently there isn't a way to add xAPI statements in Rise 360. However, we are tracking a feature request to extend xAPI reporting options when publishing from Rise. I'll include your voice in the request!
- To access reporting data from a Storyline course within Canvas LMS, the author must first publish the Storyline course to the recommended SCORM standard, and ensure the 'Course Identifier' field (Canvas course ID) is accurately populated in the publishing settings. This will allow the LMS to track learner progress and display relevant data within the reporting interface.
Also, do you mind clarifying what you meant by 'Storyline lacks the Canvas course ID'? Is the expectation to have the published course pick up the LMS-created ID for the course? If so, that is not possible as that type of communication/data is local to the 3rd party LMS being used, and not part of the Storyline specifications. However, if I misunderstood, please let me know!
Looking forward to hearing from you!
