I have TextEntry boxes set up for a data entry system simulation, which includes having learners enter phone numbers. The system requires two digit entries for day and month, 09/01/2021, for example. So, I'm trying to use a real-life simulation for this. The TextEntry fields accept two digits numbers like 09 in the example, but the triggers do not. If I change the entry field and trigger to 9/01/2021, it accepts it and completes the trigger action. I've had this issue with other software, and I'm wondering if it's an issue with Storyline 360, as well. I can't find any discussions on this topic. Does anyone have any tricks or workarounds?
On my end, I had no trouble placing zeroes in a trigger. I've attached a sample file so you can see that the trigger shown in the screenshot works without any issues:
Would you be willing to share a copy of your project file here or in private by opening a support case so we can take a closer look at how your triggers are setup? We'll delete it when we're done testing!
Mike, in your leading_0.jpg, notice in the trigger panel that the value for TextEntry8 is in double quotes. Users would need to include those quotes in the date text entry field for that trigger to fire. Is that your intent? If not, remove the quotes in that trigger.
Hmmm...I can't replicate that. I can get a trigger to fire with a text entry containing a leading zero and I can display a reference to that variable on the slide with the leading zero included.
I know you can't share your project but perhaps you can build a separate single slide .story file that illustrates the issue and post it here for us to review (or even a screenshot with the slide object(s) and trigger panel). I have a hunch something else is causing the issue but it's hard to tell with the screenshot you posted.
Sure, Steve, let me do that. The use I'm having is not the text entry not accepting the leading zero or displaying it. It's that the trigger has a Jump to Next Slide if TextEntry20 = 09/21/2021 is not working. It functions properly if the trigger is set to 9/21/2021.
Glad to say I have resolved it. I just rebuilt the slides with the issue and all is good. I still didn't find the culprit but didn't want to spend much more time figuring it out. Thanks for your help!
13 Replies
Hello Mike,
Thanks for reaching out!
On my end, I had no trouble placing zeroes in a trigger. I've attached a sample file so you can see that the trigger shown in the screenshot works without any issues:
Would you be willing to share a copy of your project file here or in private by opening a support case so we can take a closer look at how your triggers are setup? We'll delete it when we're done testing!
It sounds like yo0u maybe using a number entry
Unfortunately, we can't share files with anyone outside of the company.
I am looking for a number entry, but it also has to kat the forward slash separate.
Thanks, Joe. The issue is that it accepts the text entry 09/2102021, but the trigger doesn't recognize it.
I have the %TextEntry20% text boxes on the left to verify the entry, which it does, but the Trigger doesn't accept the leading 0.
Mike, in your leading_0.jpg, notice in the trigger panel that the value for TextEntry8 is in double quotes. Users would need to include those quotes in the date text entry field for that trigger to fire. Is that your intent? If not, remove the quotes in that trigger.
No, I was just trying to see if that would force the trigger to accept the leading 0, but it didn't, of course. I removed it.
It did accept the 0, but required the quotes, which I anticipated it would.
Hmmm...I can't replicate that. I can get a trigger to fire with a text entry containing a leading zero and I can display a reference to that variable on the slide with the leading zero included.
I know you can't share your project but perhaps you can build a separate single slide .story file that illustrates the issue and post it here for us to review (or even a screenshot with the slide object(s) and trigger panel). I have a hunch something else is causing the issue but it's hard to tell with the screenshot you posted.
Sure, Steve, let me do that. The use I'm having is not the text entry not accepting the leading zero or displaying it. It's that the trigger has a Jump to Next Slide if TextEntry20 = 09/21/2021 is not working. It functions properly if the trigger is set to 9/21/2021.
Glad to say I have resolved it. I just rebuilt the slides with the issue and all is good. I still didn't find the culprit but didn't want to spend much more time figuring it out. Thanks for your help!
Happy to learn it's sorted out, Mike. Best wishes on your project!