3 Reasons You Shouldn’t Be Afraid to Use Your Sandbox Instance
Latest posts by Rick Gilley (see all)
- 3 Reasons You Shouldn’t Be Afraid to Use Your Sandbox Instance - April 2, 2019
- 5 Tips to Avoid Critical User Acceptance Testing (UAT) Pitfalls - February 12, 2019
When our customers first start using eQuip! they are often hesitant to import new assets on their own.
They’re worried that because they don’t know how to use the system, or that they’re not tech-savvy, they’ll “mess something up.”
But it’s important to get used to importing assets because it is a task that you will most likely perform frequently in your new system. Most users don’t realize they can use the “sandbox” instance to do this without fear of mistakes.
I’m here to reassure you there’s no reason to be afraid of importing assets. Here are the top reasons why.
You will begin your implementation in a “sandbox”
Initially, the Implementation Specialist will set up a “sandbox” instance (also known as your UAT instance) for the purpose of getting your assets imported into the system. This instance will also get you accustomed to the processes and workflows in eQuip!
You will have the opportunity to work with your Implementation Specialist until your data has been imported exactly how you want it. When the system goes live, a backup of the sandbox will be created.
The sandbox instance is not the final version of your system. It is meant to allow you to experiment in eQuip! and learn how to use it. You should feel free to make changes in the sandbox instance so you can fully learn the system before it goes live.
Backup your assets
I learned the importance of backups in the early days of computer gaming from a game called Doom. In this game, you played as a space marine and fought your way through hordes of monsters while trying to reach the next level. If you did not save frequently, you risked losing your hard-earned progress and having to start all over again.
The same holds true for backing up your assets. If you don’t periodically back up (or save) your asset data, you run the risk of losing your entire system. And that’s much worse than losing your progress in a video game.
Fortunately, you can easily avoid a similar fate in eQuip! Export your list of assets into a template before importing assets to create a simple backup.
To do so, you can follow these steps:
- Log into eQuip! with your name and password
- Go to Tools > Data Import
- At the Getting Started Wizard screen choose Asset Import Template
- On the Asset Import Template screen choose the Update radio button
- Choose Export
- A template with the assets that have been successfully imported into eQuip! up to that point will automatically download (the default location is your Downloads folder)
- Make sure that you save the template to a location where you can easily locate it if need be
By following these steps, you can avoid major mistakes with your asset data. Backups should make you feel free to import asset data on your own, knowing you can easily revert any changes.
We’ve got your back
If you’re still worried about importing and changing assets in the sandbox instance, I’d like to remind you that you’re not alone in this project. As Implementation Specialists, it’s our job to support you during this process.
If you let your Implementation Specialist know that you will be importing assets, they can create a backup of your entire database (including your assets) just in case you run into an issue with an import.
By communicating with your Implementation Specialist, you can ensure any problems that may come up can be addressed quickly and easily. The database can easily be restored and will return your instance to the state it was in prior to your last import.
Importing assets into eQuip! will seem like a daunting task at first. Fortunately, your Implementation Specialist will be there to guide you until you become accustomed to the process. Taking the right steps to backup your asset data will greatly reduce the possibility of losing or corrupting your data permanently.
Don’t be afraid to play around in the sandbox. It’s there to help you learn the program and more quickly develop your permanent instance.