I'm trying to import back changes I made in a localized version into the EN one. When I import the same slide, some of the triggers in the original slide are instantaneously lost.
But, in the imported slide they are fine ...
Ideally, I would much prefer that they stay fine on the original slide, and are renamed / recreated on the imported slide.
This may explain some bugs I had beforehand, with triggers randomly stopping to work, because of the import of slides.
It is quite painful to do a full review of the module whener I import something. Is there a list somewhere of what could do wrong ?
Ok, a way to counter that (after many trial and error) is to cut the slide first, import, then paste the slide back and tadaaa, the triggers then are fine.
Hope you guys at Articulate have a look at that (but first finish Articulate AI ;) ).
EDIT : I've spoken too soon. The numeric fields have the same name than the imported ones and don't trigger the linked variables. It's ultra messed up...
I guess there's no choice left I'll have to rebuild from scratch the new changes in the slide instead of copying pasting :(
UPDATE : Guys, there's something so wrong with the import function :(
I tried to make a reduced version with just the objects I need to update and whenever I import it, that just randomly kills triggers all over my module ???
Sorry to hear that you're running into this issue.
Importing slides into a Storyline 360 project file shouldn't mess up the existing triggers so this behavior is definitely strange. If you're already working locally, I'd like to ask for the following so I can troubleshoot the behavior you're experiencing:
A copy of your project file uploaded here or through a support case so we can take a closer look at what's happening. We'll delete it when we're done testing.
4 Replies
What's strange is that even if I cancel with CTR-Z, the triggers don't revert back, they just stay messed up :(
Ok, a way to counter that (after many trial and error) is to cut the slide first, import, then paste the slide back and tadaaa, the triggers then are fine.
Hope you guys at Articulate have a look at that (but first finish Articulate AI ;) ).
EDIT : I've spoken too soon. The numeric fields have the same name than the imported ones and don't trigger the linked variables. It's ultra messed up...
I guess there's no choice left I'll have to rebuild from scratch the new changes in the slide instead of copying pasting :(
UPDATE : Guys, there's something so wrong with the import function :(
I tried to make a reduced version with just the objects I need to update and whenever I import it, that just randomly kills triggers all over my module ???
SOOOOOO FRUSTRATING !!!!
Hi Marine,
Sorry to hear that you're running into this issue.
Importing slides into a Storyline 360 project file shouldn't mess up the existing triggers so this behavior is definitely strange. If you're already working locally, I'd like to ask for the following so I can troubleshoot the behavior you're experiencing:
Looking forward to your response!