Multi-select answer options reported in wrong order
Aug 24, 2020
Pinned Reply
Hi Lindsay and Sam,
Good news! We are no longer seeing this bug in the latest version of Storyline 360 (Build 3.72.29699.0) where publishing to TinCan (xAPI) causes the order of any Multiple Response questions to be randomized or shuffled.
To insure you don't continue to see this bug download the latest version of Storyline 360 via the Articulate 360 desktop app. Here's an article on how to do that.
Please let us know if you're still noticing the issue, and we'd love to continue troubleshooting with you in a support case.
3 Replies
Hi Lindsey, I see the same problem as you. It looks to me like the report needs to map the unique IDs associated with each response rather than rely on the order that the responses appear in.
Therefore, when a users response is "choice_61EvxPj6QpD[,]choice_5mnfmaa8JSe", this would then map to the following in tincan.xml file.
Thank you Sam. I'm really hoping there's a solution to get the order to appear as it does in the file. But I appreciate your feedback!
Hi Lindsay and Sam,
Good news! We are no longer seeing this bug in the latest version of Storyline 360 (Build 3.72.29699.0) where publishing to TinCan (xAPI) causes the order of any Multiple Response questions to be randomized or shuffled.
To insure you don't continue to see this bug download the latest version of Storyline 360 via the Articulate 360 desktop app. Here's an article on how to do that.
Please let us know if you're still noticing the issue, and we'd love to continue troubleshooting with you in a support case.