Forum Discussion
Storyline 360 will not send custom XAPI statement that contains a variable
I just want it to send 1 variable that contains text, but it will not. The statement is accepted in Storyline when I create it. I am able to see other calls showing up in my LRS from the course when I publish it. But the custom XAPI statement I have attached to a button will not send. Please help me. Everything is attached here.
For anyone who finds this, god bless your soul. Here is the answer:
Start with your standard "Send XAPI Statement" trigger, chose your verb, and choose an object. I chose the slide as the object. Make sure you give it an ID.
Here's the 2 lines of code that makes everything work:
},
"result": {
"response": "%TextEntry1%"
}
}Articulate you need to update your documentation. When you negelct absolutely essential information like this, you waste countless hours of people's time. 3 days in my case! Expect an invoice in the mail.
Full code:
{ "verb": { "id": "http://adlnet.gov/expapi/verbs/answered", "display": { "en-US": "Answered" } }, "object": { "objectType": "Activity", "definition": { "name": { "en-US": "%Project.SlideTitle%" } }, "id": "%Project.ActivityId%/%Slide.Id%/Q1RP" }, "result": { "response": "%TextEntry1%" } }
I attached my storyline file as well, it has some other crazy stuff it the javascript if you dare to dream.
- Nathan_HilliardCommunity Member
In the xAPI statement, this section
"definition": { "name": { "en-US": %TextEntry1%, } },
Shouldn't the %TextEntry1% be enclosed in quotes?
- AntVecCommunity Member
Articulate issued a "fix" in Jan 2024 for this and that's what they've been replying to other posts with as the official solution. However I am not finding any success with this. I am doing nothing but using the boilerplate XAPI fucntionality on a button. 1 variable. Veracity LRS.
- AntVecCommunity Member
For anyone who finds this, god bless your soul. Here is the answer:
Start with your standard "Send XAPI Statement" trigger, chose your verb, and choose an object. I chose the slide as the object. Make sure you give it an ID.
Here's the 2 lines of code that makes everything work:
},
"result": {
"response": "%TextEntry1%"
}
}Articulate you need to update your documentation. When you negelct absolutely essential information like this, you waste countless hours of people's time. 3 days in my case! Expect an invoice in the mail.
Full code:
{ "verb": { "id": "http://adlnet.gov/expapi/verbs/answered", "display": { "en-US": "Answered" } }, "object": { "objectType": "Activity", "definition": { "name": { "en-US": "%Project.SlideTitle%" } }, "id": "%Project.ActivityId%/%Slide.Id%/Q1RP" }, "result": { "response": "%TextEntry1%" } }
I attached my storyline file as well, it has some other crazy stuff it the javascript if you dare to dream.