We've been Jamis Prime Users for 5 years now, but in all that time, other than per diem tables, we had yet to explore Import Scenarios. It was easy to push them aside to learn later, since I was so busy with other tasks. But sometimes an invest now can payoff later and, while I am still very much a beginner, I am kicking myself for taking so long to finally take the time to start learning and using them.
The hardest part was getting a working template to make the data provider, and setting up the Import Scenario itself. But once you've invested the time in setup, future usage is a breeze. I watched a two-part Jamis class, and still needed a bit of assist, but I learned so much with each step. And I’ve been very proud to have been able to figure out my most recent import scenarios without having to reach out for help. With each different scenario, I've learned something new - such as to search and research the existing templates. If you don't know how to code something, chances are one of the existing templates already in Jamis can at least demonstrate the set-up (many are dated - at least for us as we've been through quite a few Jamis versions - but they can go a long way in pointing you in the right direction). And many of them already have template data providers so you don't have to start from scratch on your own. Of course, always practice in your test site first. And make new scenarios (or even copy one) - don't edit one that's already existing. And read the wiki - there are tips in there that can save you from trying the wrong thing first.
I started with something I thought would be simple - updating attributes. We wanted to make it easier to monitor state revenue for Jobs and to add categories to Vendors (dept, contract renewal dates, a “no 1099 needed checkbox, etc.). We also added an attrribute to Employees so we can sort lists by Contract.
Then we learned how easily we could mass-upload Projects and Jobs for a new contract or extension. An extension with 30+ jobs that inputting manually would normally take hours, if not a few days, took less than an hour not counting the time to set-up the data provider. Most recently, I was able to upload over 50 milestones, each with multiple scheduled dates. A tedious, time-consuming task was transformed into something that can be done within minutes. We’re looking forward to seasonal bonuses this year as it will be the first time our payroll department won’t have to manually input 200+ employee bonuses.
My first thought now, when facing any amount of lengthy data entry, is "can we make an import scenario for that instead?"
