Sage 100

Sage Intelligence - so far I've only been installing at locations with just one user, no viewers. When you're talking multiple people - how is it setup? Install on the server - is there a client portion? How is it accessed?

SI installs at the workstation. The files are located at a server sharepoint. Just went through my first SI last week. Luckily, I had @EricAnderson on the team. I am still dizzy by all the little details that one only learns at the school of hard knocks. For the most part, all went smoothly. The major pain was the fact that they had 35 companies (i.e. a TON) of reports to migrate. And there is NO MASS migration for the files. What a pain. Debbie Hill is trying to escalate the issue. We'll see how nimble the South Africans really are. From Debbie Hill Our development team has started research and prototyped a tool which can be used to automate the copying of reports from the old repository to the new one in a few easy clicks. We are still in the alpha stages, but as you know development with Sage Intelligence moves quickly. Once it is QA approved we will integrate it into the existing Sage Intelligence so it's not a separate download (like the Report Designer Add-In). I currently do not have a release date, but will know more by Friday

Jeff when you say 35 companies with a ton of reports -- I presume you are talking about FRX reports?

@WayneSchulz - NO, they had previously migrated their reports from FRx to SI this summer. All of the reports that I refer to were SI. For some reason, SI recommended that the old data repository NOT be used for the SIv5 installation (totally parallel). So you had to export everything related to that company/report out, then back in. Perhaps the SI folks have been so busy making the product usable for the first timers, that they total forgot that migration ease of use is important for the early adoptors.

@Beth - the report repository will hold the reports and the licensing info, so as long as you have that pointing to a folder on the server (preferably not inside of the MAS90 folder where it defaults) then when you install another workstations and point to that repository on the server it will pick up the licensing and the reports - very similar to FRx, how you had the client program install on the C: Drive and the sysdata on the server. @Jeff - in the future I would just move the report repository folder to a new location or point to the old location, but based on the Sage KB article I was a little hesitant to try that because I wasn't sure how it would impact the licensing and version recognition. Most of our clients that have a lot of financial reports have them all inside of one or two front-end SI reports - that way you only have to generate one or two reports and you can have however many tabs/reports you need in the excel sheet. It might be something we could discuss with your client (I know they were an orphan and you didn't set them up that way) but I can't imagine she wants to actually run 40 reports every month when she could run one or two. Even for the reports that are not multi-company consolidations she could use the consolidated add-in report template and specifiy one company code on that particular excel sheet. Anyway, something to think about. But this was the first time I ran into the issue of 40 reports in an old version - Sage definitely needs to figure out a simple upgrade path....

THANKS EVERYONE!!!!!

I see this as a very hot issue for 2014 as more and more customers are wanting to migrate from FRX.

Here is an interesting tidbit from Jose Soeiro, the SI Product Manager: Integrated Products In reading your mail again an alternative came to mind. When you are installing Sage Intelligence on Sage 100 ERP there is an option box displayed which asks you to choose a new METADATA location, you can choose the option here to point to the old METADATA and you will then still have access to your old reports as you used in your previous version. You would then have the option to use the BULK IMPORT functionality to import the new 2014 reports into the old repository which should be a far less onerous task than the process you are working through at the moment. Too late for my client now, but it may minimize the aggravation.