Unable to delete triggers

Oct 17, 2017

Anyone know why my Delete button (trash bin icon) is grayed out? I'm unable to delete triggers. The only workaround has been to change the trigger to something else. Any ideas?

13 Replies
PTI Global

I'm having the same problem, and I've seen other users reporting it as well. In the attached, see the object Text Entry, which has three triggers. I only need one, but can't delete any of them.

The workaround is to make a copy of the control, which drops the extra triggers and assigns a new variable. I can then delete the old control.

While there is a workaround, it's very annoying and needs to be fixed, as it wastes time.

I use Storyline 360.

Alyssa Gomez

Hi PTI, thanks for sharing your file! The trigger "Set text entry equal to the typed value when the control loses focus" can't be deleted by default. That trigger is automatically added when you insert a text entry on a slide. 

I'm not sure how you had three triggers associated with one text entry, but you can remove them by deleting the text entry and replacing it with a new one. Here's a demo to show you how!

Lauren Corlett

I also have several text entry objects that have two "Set text entry equal to the typed value when the control loses focus" variables attached to it. 

And to make matters worse, when I try to change the variable to something else it only effects one of the two triggers and I don't seem to be able to affect the other one no matter which one I try to edit. 

I also can't cut and paste or delete these text entries as they are part of a series of fill in the blank questions.

I recognize that I could potentially solve the problem by rebuilding the question slides, but I have a lot of custom design and triggers (see attached file), so that process would be very complicated.

Any other suggestions?

Ashley Terwilliger-Pollard

Hi Lauren,

Thanks for sharing your file! I looked and saw a few examples where there were two triggers to set the value based on text entered, but it was adjusting different variables as this one shows: 

Were these the ones you ran into trouble with? I can see that I can't delete either of those, but I added in a new text entry and it only had one trigger assigned to it. Can you tell me more about how you added these in? 

Lauren Corlett

Hi Ashley,

Yes those were the ones I was having trouble with. In the uploaded file the one named "Ok!" was working just fine, the ones named "example #" all seemed to be having the same problem as the one you picked out.

The file I uploaded was based on an older file so I don't remember specifically, but I know the base of these slides are fill-in-the-blank questions. From there I added all of the characters/animations/additional variables. I believe I also changed the variable to attach to the custom variable I created rather than the default "text entry" variable, but I don't remember exactly. It's also likely these slides were duplicated multiple times along the way. I could see that being the cause of the problem, but I'm not sure when exactly the second variable popped up.

Update: I discovered today that trying to import the slides from another Storyline project (created in the same version) will create the double variable issue, but copy and pasting (either within the same project or from one project to another) will not create this issue. Reassigning the variable (as opposed to renaming) does not seem to be a problem.

Crystal Horn

Thanks for the insight into your process and for sharing the solution you used, Lauren!  We have seen just a handful of these situations where the text entry triggers get duplicated and are unable to be deleted, and it's difficult to nail down why it's happening.  Like you, I suspect it has to do with duplicating the slides, and reassigning vs. renaming the variables created.

If you run into this issue while creating new quiz slides or text entry interactions, though, please let us know!

Katie Riggio

Hi Emma,

Sorry to hear that you came across this, and I appreciate you sharing an example with our Support team!

Referencing the case, Lejan uncovered:

We haven't been able to recreate this on our end and we typically see this on projects with corrupted objects that prevent the trigger associated with it to be deleted. 

To get rid of the trigger, we recommend to delete the problematic object and recreate it. And to make sure that the file is stored on a local hard drive.

Let us know if there's anything else we can do!

This discussion is closed. You can start a new discussion or contact Articulate Support.