Hi,
Anyone knows where the “Import Reports” checkbox and “SSRS ReportServer Locations” fields went?
I installed 2024.1 patch #2 and updated the Administration Console, I am still having the same issue.
Thanks
Appears directly below the SSRS Database Connection box for me
I’m trying 2024.1.5 and no import reports checkbox???
Where did this go?
It looks like the reports auto deploy the first time you print them. Same with dashboards.
No go. Trying to print a job traveler:
The item ‘/{{server}}/reports/CustomReports/JobTraveler/Traveler’ cannot be found. —
1 Like
That’s a custom report. You have to manually migrate that. The checkbox on application configuration screen was to import the standard reports.
1 Like
Good catch!! The handy SSRS migration tool failed because there was no “CustomReports” folder setup, which usually gets added during report import on older versions.
I ran base JobTraveler and that single report copied over.
I then added CustomReports folder and re-ran SSRS migration tool and everything imported. Excellent.
Thanks!
1 Like
FYI others: The upgrade guide still says: “If you have SSRS Reporting Services installed, navigate to the Reporting Services sheet and
select the Import Reports check box.”
For info, the default locations for Base and custom reports has changed as of 2024.1.
Base reports are now stored in the IceCommon database which is why there is not an import reports checkbox anymore, as they do not need to be imported into SSRS.
Custom reports that are created or imported (using Epicor tools) are stored in the main Kinetic database under Ice.CustomReportStore. For existing untouched custom reports it will still look in SSRS if the report is not in the CustomReportStore table to ensure backward compatability. There is also a Ice.CustomReportStoreHistory table that store a history of the report with version and ability to restore.
see snippet below from the Whats New in 2024.1 guide.
7 Likes
So I just got off a ticket with Epicor.
Apparently this is a known issue. (that is the import reports checkbox missing). Still waiting on the problem number. And really by design
In SSRS after you deploy all you get is the shared datasource.
It appears the default RDLs get stored in the ICECommon_4_3_100.Ice.ReportStore table (yes there is a new read only db. I saw it in 2023 also.
In an attempt to deploy the reports to SSRS I took a look at the SetupData.xml file in the C:\ProgramData\Epicor\SetupInfo. I noticed that the SSRSReportDirectory key is empty, compared to 2023.2 it has the paths of the reports.zip file from the installation directory. I populated that and set the SSRSImport flag to true… It sort worked, only creating the Obsolete Stock Report and the PaymentProposal report. 
Going to do a full reinstall again and see if I can get it to work.
EDIT
No reinstall required. It appears to be by design. No import of RDLS needed to the SSRS Server.
It seems to be that you can’t use the classic report style form to copy a report style. You can in the Kinetic UI. This will be because of the lack of the RDLs residing on SSRS. (New installs only).
@josecgomez I think your SSRS migration tool has met it’s match. :(.
That being said, I am guessing an updatable dashboard would work. @aosemwengie1 Looks like being able to copy your custom reports from one environment to another, just got easier 
I am a little frustrated that they have broken classic report styles. but at least there is a work around. Just another reason to go Kinetic UI, I suppose 
8 Likes
So it looks like all the standard reports are now in the common database, which is actually a really nice design. You no longer have to deploy them to the report server at all, they just deploy themselves when you run them. And the database is shared by all instances so cuts down on a lot of redundancy.
The custom reports however are not there. Meaning nothing has changed in terms of the process to deploy custom reports to the report server.
It would be really nice if there was a way to put the custom reports into the common database. I wonder if that is something that may be on the roadmap for future? That would sure save EONs of time shuffling them around all the time. Of course there would have to be some kind of commit/publish process like there is with application studio, because you wouldn’t want a change you were testing in a dev environment to immedately impact the live environment.
2 Likes
The standard reporting dB is read only.
@Hally and @aosemwengie1 do you have your testing report data bases on the same SQL Server as the production? In other words, do they share the same SQL Server reporting Services service?
Hello @utaylor,
My testing involved rolling out the app server and SQL on separate servers. I’m using a rather unorthodox method at the moment with the SQL being a SQL Linux Docker container running on the same machine as the APP and SSRS Server install (You have to manually create the reports database if I recall. that the Epicor Reports Tempdb not SSRS)
My issue was on a fresh install of the Demo Database, and not being fully conversant with the new way that the standard RDS are deployed and how custom reports are deployed.
If you were doing an in place upgrade then I think you would not run into the same problems.
So for my testing there was not production database.
In the context of custom reports, I think if you are going to do an in place upgrade everything will work… As far as a migration goes. A solution with your reports or using the SSRS migration tool should work (I have not tested this) and for SaaS well the ongoing issue of copying Live to Test/Pilot would still be a problem…although I did do some messing around with a dashboard that uses some of the inbuilt report services to zip up said RDLS and then do an import that way… I have someone testing that for me as I am not on cloud.
Thanks for the extra info.
I just couldn’t even get the app server registered because it kept complaining about SSRS
Hmmmm event logs or install logs give any more detail? I am curious.
1 Like
I am too, do you think I should check SQL server event logs or dev app server?
SQL logs. Is the report server running? What version on SQL?
1 Like
Sorry SQL Report Server Service.
1 Like
Yeah I found the logs for SSRS.
I was hitting an issue during the registering of the app server where it was saying it didn’t have access to the report server path (which was filled in with a UNC path). The UNC path that was in there was something like this:
"If the SSRS server is on a separate machine, enter the UNC path to the
\\ReportServer directory. The current user account must have
permissions to write to this remote directory. For example, enter:
\\C$\Program Files\Microsoft SQL Server\MSRS10_
50.MSSQLSERVER\ReportingServices<RemoteName>\ReportServer.
"
