Help! Numeric entry issue

Here's the solution for the first scenario

And here's the solution for the second

Thanks Bobby for sharing here and I do see that Victor reported this to our team, and I let him know about the possible solution you shared here. That'll be good for us to investigate with! 

Thanks and feel free to keep us posted here (and we'll also keep an eye on your case!)

Hi Ashley,

Keep in mind, these are just the solutions to the scenarios themselves. Not potential solutions for the issue. I added them in case anyone wanted to play around with the file.

Always good to have those ideas, Bobby, while our team continues looking into the root cause.

Ashley,

I'm currently working with a customer support engineer to find a solution for this bug.

However, the support engineer won't give me a time frame for a solution. The best I've gotten so far is "In some cases, it may take sometime and in some, it may not."

I can't tell my client it may or may not take some time to find a fix.

I need some sort of timeline to provide to my client to resolve this issue.

Can you help or point me to someone who can assist with this?

Hi Bobby, and thanks for checking in.  I had a look at your case, and wanted to share the following in case anyone else popped into this discussion:

While our team is working on collecting information from other users, we also ran some testings on different versions of Storyline (1,2,3 and 360) and we got consistent result across the board where we were able to replicate the issue. According to our developers, this is by design and not an actual bug. 

This behavior happens for numeric variables created for numeric text entry boxes. The variable is initialized to be "Not a Number", i.e. NaN, so that no number will show up in the numeric entry field, until the user types one in. Since you're using a variable reference to reflect the content of those numeric variables, the reference will capture 'NaN'. 

To summarize, until there is a number inputted in the numeric entry field that is different from the default value, a reference to the relevant variable will read NaN, and this is by design.

Could you change the default value of the numeric variable to 1, and then trigger it to be 0 when the timeline starts?  

The file I submitted has triggers setting the value of each text input field to "0". So, if the triggers are working correctly, the text entry boxes should not be "NaN".

I've also tried setting two variables for each field. The first setting the value to "1". The second setting the value to "0". This worked when I had a low number of text entry fields (around 2-3) but when scaled to 14, I encountered the same NaN issue.

I misread your solution.

Changing the default value to 1, then adding a trigger to set the value to 0 works.

Thank you for the help!

Oh good, I'm glad that works for you in the meantime! 

To further clarify, entering the default value in the field (whether by trigger or doing it manually) will show NaN if the default is 0.  It appears to work as expected when the default is another number.

We'll keep you updated if that behavior changes!

Thank you.

That's correct. Setting the default to 1, then adding a trigger to set it back to 0 works.

Just adding two triggers ( set to 1, then set to 0) when the default is 0 does not work.

For my particular interaction, if they backspace the 0 out (leaving the entry box blank) I still get a NaN instead of the total. So, this mostly solved the problem but it's still somewhat of an issue. Even the JavaScript provided by support to change a "NaN" to "0" doesn't work.

This really should be fixed with an update.

Thanks for the breakdown, Bobby!  We've got it logged, and I'll be sure to let you know if there's an update.