Forum Discussion

LizetteChow's avatar
LizetteChow
Community Member
2 months ago

Import PowerPoint (PPTX) file into Storyline, all the images disappeared.

After importing a PowerPoint (PPTX) file into Storyline, all the images disappeared. How can I resolve this issue?

  • MattBotelho's avatar
    MattBotelho
    Community Member

    Also seeing an error here, except it went from not cooperating with the PPT assets to now crashing at every attempt at importing.

    • MattBotelho's avatar
      MattBotelho
      Community Member

      Yes, I am a "Master Developer" with storyline and been using it for 4 years. Usually don't need to submit a ticket or request unless it's beyond my control, like the never-ending "Overlapping States" issues.-

  • perhaps you need to raise a ticket then, it maybe something in the specific PPT file you are trying to import.

    • MattBotelho's avatar
      MattBotelho
      Community Member

      Yup, I have, thanks but most of us who use this program have deadlines and getting 1 reply a day isn't great, and apparently we need to advocate for issues as users so the Articulate team can "gather votes" (???) to fix it, so I am voicing my concern on these bugs to ensure it adds to the noise. 👍

      • StevenBenassi's avatar
        StevenBenassi
        Staff

        Hi MattBotelho!

        Glad to see Phil has been helping you!

        Sorry to hear you're having trouble importing PowerPoint content to Storyline 360. Smart move on opening a support case! I see that you've connected with my teammate Robert. We can continue troubleshooting through your case to keep all information in one spot.

  • Hi LizetteChow!

    Sorry to hear your PowerPoint slides aren't importing to Storyline 360 as expected!

    If you've confirmed you are working with local PowerPoint and Storyline files, please try a repair of your Storyline installation to see if that corrects the behavior. If that doesn't do the trick, please check if you can import one slide at a time regarding the PowerPoint content. If there is no issue when importing a random slide from the same deck, then this behavior is being caused by a particular PowerPoint slide.

    However, if you're still running into trouble after those steps, please share a copy of the affected PowerPoint file so we can take a closer look. Feel free to upload that here in the discussion or privately through a support case.

  • MattBotelho's avatar
    MattBotelho
    Community Member

    Thanks Steve,

    I am not requesting support here but given how long it can take for Articulate to fix issues, I am happy to lend my voice to the issues regardless of whether I've opened a case or not. The bugs in Articulate are higher than ever before and causing more delays than ever, so anything I can do to help users get their issues supported or "voted on," I will do. Appreciate the reply and have a good one.

    • PhilMayor's avatar
      PhilMayor
      Super Hero

      I understand from the CTO updates there are now less bugs. I am sure Articulate can confirm this but bugs do not need to be voted on to get fixed only feature requests.

      • MattBotelho's avatar
        MattBotelho
        Community Member

        I can assure you that is not the case. Not only does it have bugs, but I am redoing slides more than ever before due to things breaking. I work in this program most days almost all day, I could spare myself maybe 20% less time if there were no bugs.

        Here is the one I keep referring to, that has been an issue for years, but  we were told it needs "votes" to be fixed, for your reference: Overlapping States | Articulate - Community 

        The amount of time I spend fixing a state that breaks, wont flip, causes images to distort, overlap each other instead of replace each other etc., is actually pretty crazy these days, and it happens throughout my team. Not only does this affect the state/object, but the entire object then needs to be deleted and rebuilt to work again. Please see the "overlapping states" page for your reference. I will probably be told to reach out to support or maintain this info elsewhere, which I've tried through ELH and Articulate Support already but since you are replying back, I want to make sure I am highlighting a big need for improvement here rather than leaving these comments on a "we fixed it" note, since that isn't the case, respectfully.