Curiosity question with regards to Custom Reports in SSRS

We’re moving from one environment to another and we’ll do a couple of ‘refreshes’ to make sure everything comes across correctly. One of the items we had to do on the first pass was to import all of the custom reports into SSRS.

I don’t have a ton of knowledge SSRS, but if I have to separately import them, it would be logical to assume they are outside of the SQL database. Why then, when we just did a refresh are all the custom reports gone and in need of reimporting?

“Custom SSRS” reports can be taken to mean a couple of different things.

Do you mean:

  • Customized versions of the reports that come with Epicor (like a customized version of OrderAck)?
    If so, that has several components:
    • A customized RDD
    • The custom RDL files
    • Report Styles
  • BAQ Reports
    • BAQs
    • BAQ Report
    • Report Styles
    • The RDL(s)

Everything but the RDLs should reside in the Erp DB.

The RDLs reside in the SSRS DB

1 Like

As I thought it was structured.

So then once the RDLs are loaded into the SSRS DB, why would they not be there after a refresh of the Erp DB?

Unless someone wiped the SSRS Db to create a clean restore?

When the environment is created in the EAC (Epicor Admin Console), you specify a name for SSRS.

I don’t recall all the details as its been years since I created a new environment (or even used EAC).

One thing I originally did (which I’m sure I’ll get some dirty looks about) was to use the same SSRS for both my PROD and my TEST environments. This alleviated needing to copy the SSRS stuff from my LIVE SSRS stores to a TEST SSRS stores. The down side was that fiddling around with reports in TEST could actually change the RDL, whch the same RDL is also being used in PROD.

The EAC setting I was referring to is shown in this post:

I would refer to this from EpicCare.

https://epiccare.epicor.com/epiccare?id=epiccare_kb_article&sys_id=657516251bd1ed5002b777f1cd4bcb0d