Migrating from 10.1.400 to 10.2.300 (on new servers too), and I setup the SSRS on the new servers to use a unique report root for each App. I copied the the custom reports over by they all have a “bad” Data Source.
Original (and current Production) environment
SSRS report root (in EAC App Config):
<blank>
Path to a custom version of the OrderAck:
Home > reports > CustomReports > SalesOrderAcknowledgment > SOForm-MATCOR_20180707a
A data source in a “built-in” report for 10.2.300 is
UAT_102300/reports/SharedReportDataSource
Browsing Home > UAT_102300 > Reports shows no objects named SharedReportDataSource.
Is that actually a DB on the SQL server?
Is there anyway to mass (or easily) update the data source value in every one of my custom reports being copied from my 10.1 environment to the new 10.2 one?
Or should I just setup my 10.2 environment like I had 10.1 (with all Apps sharing the same report storage?
How did you copy the reports to the new environment? If you use Epicor (either through Report Style > Upload or through Solution Workbench), it should automatically update the Data Source for you.
We have a SharedReportDataSource in each of our environments’ directories (/Epicor/reports/SharedReportDataSource, /EpicorTest/reports/SharedReportDataSource, etc.). It contains a connection string to the reporting database Epicor exports the report data to.
We split our reports so that we can make changes to report RDLs in the Test or Pilot environments without affecting live reports. I know in 10.2.300 you can use the SSRS report designer to have a “temporary” version of the report without publishing it, but this lets me make changes and have users test with more than just the sample data.
The URL will be the same as you entered in the Admin Console for Reporting Services, just change /ReportServer to /Reports. This will bring you to the portal in Dan’s post where you can view the RDLs and Shared Data Sources (which are all technically stored in the SSRS database so they aren’t real “files”).
Did you locate the datasource by opening IE and going to SSRS reports? If you have, you could technically just copy this source to UAT_102300/reports/
Then you just have to make sure the connection string is pointing to the correct database.