Forum Discussion
Scorm package already exists?
I've got a course I've built in Rise that is mostly made up of videos. In preview, it runs as planned and each video only starts when you click on it. On the Review website, when you open a module, all of the videos in that module start all at the same time.
I figured I would load it into our Stage environment of the LMS to see what it does there, but I am getting an error message that says The file could not be uploaded successfully because the activity code is not unique. Enter another activity code. I cannot see anywhere in Rise where I can change the identifier like I can in Storyline. I also don't see how an activity code already exists for the course as it is still in development.
So I guess I have two questions. I've looked at discussions on here about videos playing and not playing and how it can vary depending on which browser is being used. For this particular course, they are trigger-started in Storyline and uploaded from the review website (all have cc). Is there anything in Rise I can do to make sure this trigger is enforced?
Question number two is why would the activity code already exist? The only way I can see this is if Rise randomly generates a code as metadata and someone else in the organization has uploaded something with the same metadata already. Is there a way in Rise to change identifying information like there is in Storyline? I haven't been able to find one but if there is a way, I'm sure someone else has.
Sorry for the long post. I am quite frustrated at this point so any assistance will be greatly appreciated!
Hi DianeBrochu,
Thanks for reaching out!
I understand how frustrating it can be when your course isn't playing as expected. I've opened a support case on your behalf so we can investigate what's going on. You'll be hearing from one of our Support Engineers soon via email.
Hi DianeBrochu,
Thanks for reaching out!
I understand how frustrating it can be when your course isn't playing as expected. I've opened a support case on your behalf so we can investigate what's going on. You'll be hearing from one of our Support Engineers soon via email.