We’re in the process of upgrading to Kinetic 2024.1 and have found out that the custom SSRS report do NOT automatically upgrade. We’re on-prem and are building out a new instance of the software and database which will support the converted data once the final conversion step takes place. The new version of Kinetic works with a new version of SSRS so we’re set up with that new version but on initial conversion there are NO SSRS reports visible. We’ve been told that the “new” way it works is that on the first running of a report it then populates the SSRS file(s) associated with that report. The methodology suggested to us for custom reports is to 1) run the report with std SSRS report style, 2) copy the std file(s) to the custom folder and then customize to fit or download the file(s) from the old version and upload to the new custom folder. This is a MASSIVE undertaking to be done individually by report and I’m wondering if there’s a faster/bater way that’s been undertaken out there. I was also told that creating a solution on the old and importing to the new platform would also work but again it’s a royal pain to try to grab everything and not miss anything. Any suggestions which have worked for others???
The basic process is not much different than previous upgrades with Epicor and SSRS.
This only refers to custom reports, stock reports work basically like you described, they will show up in the structure as you run them.
- The first thing I do is download/upload all of the custom reports under my CustomReports folder to the new instance
- Ensure all reports point to the new report server dataset.
- Test your individual custom reports to see what does & does not work.
- Fix the RDD, report, etc as needed.
All of our customer/vendor facing reports are customized along with a good many of our internal ones as well and the only one that ever gives me issues beyond the odd field being changed is the ARForm, this round of upgrades I had to revert to the Epicor base report and RDD, customize the RDD and redo the form from scratch but pretty much every other one this time around just worked.
Use Jose’s SSRS migration tool if you’re on premise. Will save you hours of work. Epicor SSRS Migration Tool
Can confirm that my most recent migration to 2024 also required this. There were, however, some less than “best practice” modifications made to this report in this instance. I’m not sure the trouble was an Epicor problem in my case.
Another option is to use the Solution Workbench. You can build a Solution that holds the Report Style, Report Data Definition, and the RDL files all in once place if you so choose. You can also use this for BAQ Reports.
Starting in Kinetic 2024, the standard reprots are stored in the db now as I recall. Your custom ones however will still need to be copied to/from Production/Pilot/Test from time to time even after your upgrade to 2024 is completed. So this is something you will need to be able to do from time to time.
If the database is upgraded, the rdds are already in the database. The last thing you want to do is import them from another database using solution workbench, which will wipe out all your valid/default settings on the companies tab.
Just use the migration tool to move the rdls and then test to see what is broken.
The same goes for me throughout several upgrades. Epicor support recommends recreating your custom RDD, but I found I was able to open the new base RDD in one window and my custom one in another. Then I just paste inserted the missing fields so my custom RDD works.
Thanks for sharing that tip with us Jenn!
And I have ALWAYS had to fix the RDD for ARForm. Always.
10.2 to 2024? Once you have so e this the first time custom reports will be in the database going forward so you should be good after that.
Thanks for the info on that migration tool. I have a couple of questions on it before I take the leap and run it. First off will this work w/o problems when moving to the new version of SSRS associated with 2024.1? Second, from where does this have to be executed? Does it have to be on one of the servers (to or from) which is noted in the execution parameters or can it be run from my PC (which has access to both of the servers)? Third, has this ever been run by Epicor as far as their input on whether it could work and whether it isn’t spiked w/ malware or ???. I know the likelihood of Epicor providing any input is probably remote since the lawyers will probably say they can’t take even a wiff of liability with it but just asking.
I haven’t tried it on 2024 because I’m on cloud now, but I used it on multiple prior versions and never had a problem. As long as your computer can access the server path you don’t have to be on the server itself.