Nan Error in Results Slide

Hello!

My team and I are making the transition from Captivate to the Articulate 360 Suite. I have some basic experience with SL but look forward to rockin' socks as I get better and better.

Anyway, a problem we had in Captivate (9 specifically) was the Nan error. I've seen several threads regarding numeric entries and Nan errors, but ours only seemed to come up on Results slides and when our module had a pre-test. FYI: The Results slide did not include pre-test results; it just seemed to only happen when a pre-test was in the module somewhere. 

Have any of you had a similar problem with the Nan error coming up on Results slides in SL? I'd love to get in front of this issue before we start using SL for everything. Thanks! 

19 Replies
Laurie Foberg

I've seen the "NaN" calculation as well today in both preview mode and when published to LMS and viewed from LMS. In our course we have one final test. On the results slide after failing the test, there is a Retry Test button. When that button is clicked, there is a trigger that resets the results of the final Test. However, once clicked, the learner's score changes to "NaN". Although this also directs them to the Intro slide to the test, it is still a noticeable change. I'm attaching a screen capture here for reference.

Ashley Terwilliger

Hi Laurie,

I'm glad to hear that at least! It is going to reset the score, but that should happen so quickly before jumping back to the first slide it's often not something folks see (either the NaN or the 0). Are you seeing this just in preview, or also in your published output?

If you wanted to share your .story file I'm happy to take a look at it and do some additional testing.

Ashley Terwilliger

Hi Alexandra, 

We've seen this happen under two conditions, do either of these match what you're seeing: 

  • HTML5: Results.ScorePercent shows as "Nan" for a split second when Retrying when there's a Question bank question with a Jump-to-specific-slide-number trigger in the feedback layers.
  • In Flash, the Results.ScorePercent would show as 0 when retrying.

If so, it's an open issue with our team, and we'll keep you posted here! If you think you've run into something else, could you share a copy of your .story file with us so that we can take a look? 

You can share it publicly here, or send it to our Support Team here. We'll delete it when done troubleshooting.