Version Control Issues, Edits not saving

Hi Marisa

Articulate recommend that you work locally with the SL files to avoid issues such as you are mentioning.  

Can you download the file, work on it and then upload when finished...I think that would be a better way for you to work and avoid the synching/loss of work issues.

I've had similar issues working with PowerPoint on SharePoint. I agree with Wendy that the safest thing you can do is work on a local version of the file and upload to SharePoint when you're finished each day.

Thank you both for the suggestion! That is our current process, so I’ll edit my post to be more specific. Have either of you, perhaps, noticed a certain amount of time needed for files to fully sync?

I have used Storyline in a scenario where we used Git to store our files. The advantage to Git over Sharepoint is that it tells you when you are trying to save a file that conflicts with the files that are in the repository. I don't know what your method of making sure 2 people aren't modifying the same course at the same time or assuming they're starting from the most recent when they aren't but with just 4 people on a team we ran into sync issues a lot.

Thanks, Diane! I'm not familiar with Git, but will look into it. We're pretty invested in SP at this point, but there's always new/better technologies.

Our workflow is pretty well-structured, so we (luckily!) don't often have the types of sync and version control issues you experienced.

Hello all - was this issue ever resolved? I am experiencing the same problem and was wondering if anyone has a solution. My team's workflow is the same: work in the SL locally offline, then upload to SharePoint at the close of business. For internal reasons, we have to use SharePoint to store the files. Lately I have been noticing way more instances of edits that were made, but reverting when I reopen the file. Any follow-up is much appreciated. 

Hi Madeline,

I wanted to share some tips that I hope will help when working in a collaborative environment. It is best to continue working on your Storyline projects locally. When sharing the course file with your team onto a network drive, the workflow outlined here should help: 

• Storyline: Recommended Workflow for Collaborative Network Environments

Please let us know if you have any questions about this! We are happy to help! 

Some days I feel like I am going crazy, but reading this post makes me think it's not me. This week, we had three instances where we signed off on a SL360 file, posted it to our LMS, and then a user reported errors in the file. Mostly it had to do with the timeline not ending at the end of an audio clip. In one file we had 11 instances out of 35 slides. We have pretty good quality control to no miss something that blatant. For this to happen in three different files, is when we became concerned.

We now have a process that we print a log sheet for each file showing every change, and date/sign when updated. We started keeping multiple daily incremental copies of files, and we are doing two final rounds of proofing. The amount of overhead has risen dramatically.

The file that really bothered us followed this route. File A: proofed no errors. File B: is a copy of file and then the name changed (all done through Windows file explorer). We go to edit File B and the timelines do not match File A on multiple (not all) slides. There is no reason any of our developers would have increased the timelines to extend beyond the audio, and certainly not multiple times.

We work locally. At end of day we manually copy files to a Windows server. Another user (or same) will download the file from server and work on it the following day. We are NOT uploading to Sharepoint though our organization does use it. Just thought I would share.