Numeric entry field issue with specific numbers
Nov 13, 2019
I'm having problems with Storyline number entry fields not accepting a very specific range of numbers in a variable.
I have a question to make that has a selection of number entries. It is set up as a Pick One style question where a correct button, positioned off screen, is selected after the correct number is entered into the field and the submit button is pressed. I have made many of these question types in the past, some of which with big tables filled with lots of number fields and there have been no problems. The problem I'm having with this one seems to be specific to the number I need to make the correct answer, as well as others in the same region.
I made a basic version of the question for testing purposes and I'll attach it here. The number I need to be correct is 16802.53 but it's always popping up as incorrect. I tried it with the same number but changing the last 3 to a 2 and that worked fine, I tried it with only 1 decimal place as .5 and .6 and it worked fine, I tried changing the last 3 to a 4, 5 and 6. These ones also didn't work, but changing it to a 7 worked fine. I multiplied the number by 10 (168020.53) and that one also didn't work. I tried small numbers (3 and 3.53) and those worked fine.
What worked and what didn't:
3 - Works
3.53 - Works
16802.5 - Works
16802.52 - Works
16802.53 - Doesn’t Work
16802.54 - Doesn’t Work
16802.55 - Doesn’t Work
16802.56 - Doesn’t Work
16802.57 - Works
16802.6 - Works
168020.53 - Doesn’t Work
This list is also in the attached story file for easy reference.
I'm not sure what's going on or why these specific numbers won't work but I'm hoping someone could maybe have an answer for this before I try to get the question rewritten or use a text entry field instead.
Not sure if it's similar to the issue found in this thread: https://community.articulate.com/discussions/articulate-storyline/data-entry-fields-and-decimals but when I enter the number from there into the trigger in my file (922185.33) Storyline decides to change the last decimal point from a 3 to a 1 (922185.31) which . Neither answer works as correct. This number isn't important for what I'm currently working on but thought it was interesting as it's another that doesn't work but in a different way. I tried a few other extra numbers in the range of this number too and I'm getting similar weird results with Storyline changing the number in the trigger.
Am I just unlucky that I happen to need to use one of a selection of numbers that just doesn't work in Storyline for some weird reason? Is this a known issue? Will I just need to do a work around and hope that I don't bump into any of these numbers again in the future?
3 Replies
This post was removed by the author
I created a ticket regarding this issue and it's being looked into. For anyone in the future that might run into a similar issue there's a workaround as suggested by someone that replied to my ticket.
The workaround: Create a new numerical variable with the default value set as the correct answer then set the submit trigger to if the field entry equals the new variable rather than the actual number.
I'll attach an updated version of the file here in case it's of use to anyone for reference. Hopefully the team can get to the bottom of whatever's causing the issue and can find a fix for it for a future update.
Hello there, John. Thanks for bringing this to our attention!
It's much appreciated that you shared what worked with everyone, as it'll help those who come across this discussion!
I'll follow your case with Christopher as it progresses to share any more relevant information here, too. Please let us know if you need anything else!
Thanks Katie, I will.
This discussion is closed. You can start a new discussion or contact Articulate Support.