Estimated Time To Read This: 2 – 3 minutes
We’ve all been there at one time or another. With confidence we go and make a change and voila, it looks beautiful. After we celebrate our prowless, a few days later we go over what we did and notice that something just isn’t right. Why are all my people at the wrong location? Why are they assigned to the wrong school?

At times like these, the existence of a good backup and recovery strategy is paramount. In the case above, the creation of a backup before the change would have been a good idea. The old information could be restored and the change could have been applied again – except correctly this time. Backups are good; knowing where to find the backup is even better. There is no use in making a backup if no-one knows where to find it or how to use it. At CoreSolutions, one approach that we use to help with these mis-steps is whenever we install a new application, we highly recommend installing a sandbox at the same time. If there are changes to be made to an installation, always try it on the sandbox first. If it doesn’t work, make some changes and try again. The sandbox is a proving ground for your change – by changing the sandbox first, you eliminate much of the trial and error that is associated with product changes and upgrades.
Don’t have a sandbox? Please frantically email us at your earliest convenience. ContinuED / PD Place sandboxes are a fun places to enjoy once all the pebbles have been raked aside.
Mark





