Forum Discussion
Missing SL 360 File
As rachelatkaiser notes - and many others on this forum - working off OneDrive or any shared network location is asking for trouble. Better to keep the work only in your C:\[computername]\Documents\My Articulate Projects location.
That being said - one location that you may want to check is your Storyline temporary files. These are at C:\ProgramData\Articulate\360\Temp - our IT policy now prohibits me from digging in there, but when I have needed it before I was able to locate a nearest-to-the-last-copy-that-I-could-remember story file. Good luck.
JHauglie Duly noted and lesson learned! I will save my projects as recommended. I checked the temp location and unable to access it either. So, I assume our IT dept prohibits access as well.
The good news is that I selected the box to save the project to the cloud when I published it to Review 360. This allowed me to download the most recent SL file from Review 360. Thanks for responding!
Update: IT doesn't allow me to save to that directory. Therefore, they will need to provide a solution so that I can successfully backup files. Our IT department isn't familiar with Articulate. So, I may need memory sticks until there is a solution.
Our team's best practices for this problem are to:
- Make sure your "working files" are on your local system only (while you are working on them).
- At the end of the day/week/revision cycle (you get to establish this), copy the entire directory to your OneDrive location. (Some of us do this daily, others do it weekly.)
- When the module is finished (we do get some of these!), we put a copy of the final story file and any other related files (resources, for example) on a shared network location. Each of the team members also keeps a copy of the same package, and we try to make sure that their final OneDrive version is the same as the shared network location version.
So far (since we made the transition to OneDrive a few years ago), we have only had a few instances where the "final" version did not align with the individual's "final" version. But it's made a strong case for consistent versioning and revision / naming controls.
Glad you are working things out!