Forum Discussion
Reach 360 Overwriting Uploads from Storyline
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:
- Does the issue only happen to your Module 4 project file?
- When publishing both Module 3 and Module. 4, did you check to make sure that they each have unique identifiers in their publishing settings?
- Try importing the slides in your Module 4 project over to a new Storyline 360 project file. Does the issue still occur when you publish this new project file to Reach 360?
Looking forward to hearing from you!
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
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?