Forum Discussion

PaulAbbott's avatar
PaulAbbott
Community Member
5 months ago
Solved

Reach 360 Overwriting Uploads from Storyline

Hi,

I'm using the (included tier) of Reach for the first time.

 

I've been uploading directly from Storyline and it's worked for the first couple of modules I've uploaded, but then Module 4 seems to upload 'over' Module 3 - i.e. it overwrites it as an update, despite being a separate named file in Storyline with different content.

I'm essentially stuck now unable to upload any more material as at least a couple of modules are suffering from this issue. 


Any experience of this from anyone, or any advice?

Thanks!

  • Hello PaulAbbott ,

    Thanks for reaching out and I'm sorry to hear that you ran into this snag!

    I'd like to ask a few questions to help clarify your experience and identify a possible solution:

    Looking forward to hearing from you!

     

  • PaulAbbott's avatar
    PaulAbbott
    Community Member

    Hi - thanks, JoseTansengco - it seems to have been the identifiers for the modules. Changing the identifier itself didn't help but a rebuild/import into a new project seems to have. 

    • PeggyHarris-ad9's avatar
      PeggyHarris-ad9
      Community Member

      This solution (updating the ID) did not work for me.  I am hesitant to import all slides to a new project.  We are evaluating Reach to see if we want to change from a different LMS.  If it requires rebuilding every course into a new project, that seems like a workaround and not a solution. Please clarify if I am misinterpreting this solution. JoseTansengco 

      • JoseTansengco's avatar
        JoseTansengco
        Staff

        Hi PeggyHarris-ad9,

        Sorry to hear that you ran into this issue. 

        Yes, you are correct. The solution described in this thread is to import the content into a new Storyline 360 project file because doing so automatically generates a new identifier for the course. Typically, this step is unnecessary since the system should automatically sort itself out. We're also not seeing this issue being reported by most of our users, so it would appear that publishing normally works for them. 
        With that being said, would you mind making a quick Peek 360 recording of the behavior to help us investigate what's happening? And would you mind repairing your Storyline 360 installation to see if this fixes the issue? 

  • Hello PaulAbbott ,

    Thanks for reaching out and I'm sorry to hear that you ran into this snag!

    I'd like to ask a few questions to help clarify your experience and identify a possible solution:

    Looking forward to hearing from you!