Uplifting Custom Reports to Upgraded Environment

Epicor ERP 10
1

Hello all,

We are in the process of upgrading from 10.1.400.2 to 10.2. I have access to our Vanilla and custom environments after the first data pass and have completed the post upgrade checklist Epicor supplied.

HOWEVER, I am struggling to follow the documentation when it comes to uplifting custom reports. I have a complete list of custom reports that I obtained from the ERP Analyzer tool and am now in the “Upgrade Using Epicor Tools” guide. It tells me I should be able to download my custom reports from the “Report Style” screen in our production environment and then upload them to the correct report style in the new environment:

image
image.png976×443 51.7 KB

When I try to download a custom report though, Epicor generates this error. It appears to be duplicating the “reports/customreports” portion of the path and cant find the report:

1
1.png862×595 34 KB

The style itself looks like this:

image
image.png853×461 21.3 KB

Can anyone shed any light on why I can’t download these custom reports from our current production environment?

Thanks,

Alice

2

I kind of remember this path duplication in the SSRS setup but… I don’t have the details handy.
Maybe Application Server Setup - Reporting Services sheet?

In the mean time I wonder…
Can you run the the Std report on any of the systems?
----- and how about the custom report(s)?

Or can you duplicate either a Std or Custom report?

  • Actions --> Copy Report Style?

Or finally, can you access your SSRS report manager in your browser and see the servers/report folders?

3

Hello Alice,

I just use the same root folder name on export and import, e.g. c:\reports

Don’t use Custom Report in the process.

Mark W.

4

Thank you Mark. I used the C:\reports and that works great for most of them except for the ones that have subreports (or thats what appears to be hanging it up).

Here’s how the custom traveler appears on our production report server - the main report and subreports are contained in one folder called “Job Traveler” :

image
image.png1546×357 19.7 KB

image
image.png888×621 37.7 KB

Its the same thing when both the report and the subreport are loose in the custom reports folder:

image
image.png1044×629 52.4 KB

1
1.png1323×617 31.1 KB

Are the subreports somehow causing this duplication in the path??

When I try to download from report style screen into the C:/reports, it can’t locate the first of the subreports:

5

What happens if you just select My Documents - as a test?

6

Have you tried renaming the “Job Traveler” folder to remove the space?

7

I tried…no luck :frowning:

Thank you though.

8

I feel like this is an issue with duplicating the path of subreports:

Here’s is how the subreport is referenced within this style of JobTrav:

2
2.png926×120 4.31 KB

And here is Epicor duplicating that part of the path when it looks for the first subreport in folder:

3
3.png888×621 39.5 KB

Is there another way to reference the subreport within the main JobTraveler to avoid this path issue?

Alice

9

All of my subreports are referenced directly. The path isn’t needed since they’re in the same folder.

image
image.png876×204 10.7 KB

1 Like
10

aha!! I will try that.

11

It worked!!! Thank you so much! I’ve been messing with this for days.

1 Like
12

I would just use ReportSync to copy the entire CustomReports folder to my 10.1 server, then use it upload them to the 10.2 server.

image
image.png691×620 36.5 KB

Apparently it even has a Sync function. But I’d be more cautious and do it as two steps.

  1. Download the RDL “files” from my old SQL server.
  2. Upload them to the new SQL server

EDIT

I use this program to regularly “backup” the RDL “files”. Those archives have saved me more than once - especially before i knew about the dangers of “Sync Dataset” on the Report Style

1 Like
13

Well, this looks useful…how is it for copying reports between environments? Do you have to update all the data sources?

14

This only deals with the RDL “files”. It is unaware of the E10 app. I put files in quotes as they don’t exist as files on the server, but rather as chunks of data equal to the contents of the “file”.

Here’s what I believe each button does:

  • Download: Retrieves the reports in the selected directory (and sub-directories) from the SQl Server specified in the Source SSRS Web Service, saving them to the folder specified in the Local path text box.
  • Upload: Sends the the reports in the folder specified in the Local path text box, to the SQl Server specified in the Destination SSRS Web Service.
  • Sync: THIS IS JUST A GUESS!! I think it compares the contents of source Web service to that of the destination, and updates any missing folders and RDLs. I don’t know what it does if the RDL exists in both source and destination. I don’t know what it does if the RDL exists on both and the one on the Destination is newer. It might:
    • Ignore the one on the source.
    • Copy the older one from the source, overwriting the newer one on the destination
    • Copy the newer one from the destination, overwriting the older one on the source

If you did an upgrade by restoring a backup of your live DB to a new E10.2 App, then all the data definitions and report styles (including their paths to custom reports) should come over.

15

P.S. - I’m in the middle of a 10.1.400 to 10.2.300 upgrade too. I’ve hit a roadblock as our SQL team is having issues getting the SSRS service running. :frowning:

16

I hope to start testing that upgrade in a month or so, but our entire SQL and Epicor team consists of me. Can’t wait…

17

You might be luckier. Our SQL team is difficult to deal with.

I’ve had no problem installing 10.2 on the App server, restoring a backup of the 10.1.400 DB, converting it to 10.2.300. Everything works except SSRS. I can only deploy the apps when SSRS is not enabled.

Epicor says it’s a SQL SSRQ installation problem, our DB people think otherwise - even though the SQL Server’s Event viewer shows error messages related to SSRS, even when the E10 App pools are all stopped. :hot_face:

18

I’ve dealt with enough screwy, counter-intuitive computer problems to know it could still somehow be an Epicor fault…but that sounds like SSRS is the obvious place to exhaust all possibilities first. I wish you luck!