Forum Discussion

JustinLovett-75's avatar
JustinLovett-75
Community Member
5 years ago

Rise 360 not reporting all question data to LMS

I currently have a Rise course with a quiz setup inside. The quiz has 5 questions, 3 multiple choice, two multiple choice multiple select. When I pull the LMS report for users who have completed the course I am only able to see 3 of my 5 questions come back in the SCORM data.

 

It's the same three questions consistently, and it's 2 mc and 1 mcms, so I am not sure if it's just one type of question or another not reporting but it's really stumping me.

 

Currently we are tracking using completion of the Rise course and not the Quiz results. Should we switch it over to ensure all results are captured? If so, then why are some being reported and others are not within the LMS (published for Scorm 2004 3rd edition) with the current completion setting?

 

Regards,

Justin

20 Replies

  • Yes, I can verify that in Rise the IDs of questions 3, 4 and 5 are the same, which means it only gets reported once to the LMS. I am experimenting now with ways to delete/add new questions with new ids.

  • Here is the SCORM report from Scorm Cloud after I deleted the duplicated questions (the two that weren't reporting) and added them in from scratch again. Notice how the identifier has now changed, this translates to me duplicates = bad.

     

    cmi.interactions.0

    cmi.interactions.0.id: Knowledge_Check:_Tec_In_technical_recruit_0
    cmi.interactions.0.type: Choice
    cmi.interactions.0.objectives.0.id: 0
    cmi.interactions.0.timestamp: 2020-05-04T11:48:01.0-07
    cmi.interactions.0.correct_responses.0.pattern: L5_SDE__L6_SDM__L6_TPM
    cmi.interactions.0.weighting: 1
    cmi.interactions.0.learner_response: L5_SDE__L6_SDM__L6_TPM
    cmi.interactions.0.result: correct
    cmi.interactions.0.latency: 0000:00:07.31
    cmi.interactions.0.description: Q?

    cmi.interactions.1

    cmi.interactions.1.id: Knowledge_Check:_Tec_If_you_identify_a_L6_0
    cmi.interactions.1.type: Choice
    cmi.interactions.1.objectives.0.id: 0
    cmi.interactions.1.timestamp: 2020-05-04T11:48:07.0-07
    cmi.interactions.1.correct_responses.0.pattern: Identify_an_L6_SDE_specialty_recruiter_and_partner_with_them
    cmi.interactions.1.weighting: 1
    cmi.interactions.1.learner_response: Identify_an_L6_SDE_specialty_recruiter_and_partner_with_them
    cmi.interactions.1.result: correct
    cmi.interactions.1.latency: 0000:00:02.93
    cmi.interactions.1.description: Q?

    cmi.interactions.2

    cmi.interactions.2.id: Knowledge_Check:_Tec_Which_of_the_followi_0
    cmi.interactions.2.type: Choice
    cmi.interactions.2.objectives.0.id: 0
    cmi.interactions.2.timestamp: 2020-05-04T11:48:11.0-07
    cmi.interactions.2.correct_responses.0.pattern: PHP_and_Javascript
    cmi.interactions.2.weighting: 1
    cmi.interactions.2.learner_response: PHP_and_Javascript
    cmi.interactions.2.result: correct
    cmi.interactions.2.latency: 0000:00:01.89
    cmi.interactions.2.description: Q?

    cmi.interactions.3

    cmi.interactions.3.id: Knowledge_Check:_Tec_From_the_following_r_0
    cmi.interactions.3.type: Choice
    cmi.interactions.3.objectives.0.id: 0
    cmi.interactions.3.timestamp: 2020-05-04T11:48:16.0-07
    cmi.interactions.3.correct_responses.0.pattern: L6_Technical_Program_Manager
    cmi.interactions.3.weighting: 1
    cmi.interactions.3.learner_response: L6_TPM_and_L6_SDM
    cmi.interactions.3.result: incorrect
    cmi.interactions.3.latency: 0000:00:02.15
    cmi.interactions.3.description: Q?

    cmi.interactions.4

    cmi.interactions.4.id: Knowledge_Check:_Tec_Of_the_following_whi_0
    cmi.interactions.4.type: Choice
    cmi.interactions.4.objectives.0.id: 0
    cmi.interactions.4.timestamp: 2020-05-04T11:48:21.0-07
    cmi.interactions.4.correct_responses.0.pattern: Active_coding_experience_in_an_Object_Oriented_language
    cmi.interactions.4.weighting: 1
    cmi.interactions.4.learner_response: Active_coding_experience_in_an_Object_Oriented_language
    cmi.interactions.4.result: correct
    cmi.interactions.4.latency: 0000:00:02.22
    cmi.interactions.4.description: Q?

  • Hi Alyssa,

    We're having the same problem. And confirming the comments above - seems to have something to do with the question name. Depending on the LMS only 9 or 10 of 11 Questions are being reported. The ones that don't get reported all begin "What's the answer to..." which is where the ID is cut, so I'm guessing that's the issue? Would exporting to SCORM 2004 solve this problem? Or is there a fix in the pipeline?

    Thanks,

    Curtis

  • Hello, Curtis! Thanks for letting us know what's going on. It sounds like questions that begin with a similar phrase are receiving an identical question ID. Please try these steps, and let me know if you see an improvement:

    1. Recreate the affected questions, and use the same wording as the original questions.
    2. Publish for SCORM 2004 - 4th edition.
    3. Test the output in your LMS.

    If you are still having issues with reporting, please share the SCORM output file with our team by opening a case. We'll take a closer look at it!

  • I carefully reworded each of my similar questions and that corrected the issue.

    • Crystal-Horn's avatar
      Crystal-Horn
      Staff

      Thank you so much for that update, Justin.

      I'm going to look into this issue to see if there's something we can improve on our end to help with reporting on similarly stated questions.

    • hazelB's avatar
      hazelB
      Staff

      Yes SibaPrasad, please republish the course and upload it to your LMS. 

      If  you're still having  issues, you can open a case here so that one of our technical support engineers can take a look