Is SSRS Subreport Linking Possible in Epicor SaaS/Cloud?

Kinetic ERP
, , ,
1

Hi Epicor community,

Working on a custom SSRS report in Epicor SaaS where I need to embed a PartOnHand BAQ report as a subreport within an Order Acknowledgement main report. Getting consistent path errors like:

/reports/CustomReports/OrderAck/OrderAck;reports/CustomReports/PartOnHandRpt3/PartOnHandRpt3

Specific questions:

  1. Is traditional SSRS subreport functionality supported in Epicor SaaS/Cloud environments at all? (No Report Builder/SSRS Manager access)
  2. What’s the correct Epicor SaaS workflow for “subreport-like” functionality - RDD multi-BAQ datasets only?
  3. Anyone successfully implemented dynamic BAQ data in subreports via SaaS? Workarounds for TableGuid parameter passing?

Context: On-prem works fine with separate subreport items and proper /reports/ paths, but SaaS Report Style analysis fails validation.

Epicor Version: SaaS Kinetic (2025.2.5)
Error: “The path of the item is not valid” during RDL status retrieval

Any guidance or confirmed limitations appreciated!

Thanks,
Kshitij Jadhav - ERP Developer

1 Like
2

You can’t list multiple reports like that.

  1. Copy the standard style to a new style
  2. Update RDD if needed (optional)
  3. Edit the rdl as needed. Embed any subreports you want the same way you normally would.
  4. Upload via report style to publish. That will create the subreport on the server

Do not explicitly reference the subreport anywhere in report style. The only reference is inside the rdl that you upload. Make sure your main rdl and your subreport rdl exist in the same subfolder. The subreport can only reference the same rdd as your main rdl.

6 Likes
3

Since I am using Epicor SaaS, I don’t have access to the report folder on the server. Because of this restriction, I’m unable to place the main RDL and subreport RDL in the same folder or manually manage subreport files on the server.

Therefore, adding or referencing subreports in the same way as on-premise Epicor is not possible in my environment. If there is an alternative approach supported for Epicor SaaS (such as embedding logic in a single RDL or using supported deployment methods), I can implement that instead.

1 Like
4

You don’t need to. You have the report and subreport in the same folder or zip on your machine, and upload it.

Go see how the packslip report style is set up.

2 Likes
5

Pretty sure it is a comma used as a separator instead of a semicolon.

Also, I’m not sure but I think I’ve always seen the subreport in the same folder, e.g.:

/reports/CustomReports/MyNewOrderAck/OrderAck,reports/CustomReports/MyNewOrderAck/PartOnHandRpt3

2 Likes
6

I’m facing a similar issue. I created a separate Report Style and configured it to use the same report location as the main report. However, when I embed this report as a subreport in the main RDL and try to preview it, an error is thrown.

Additionally, although the subreport is uploaded and visible on the report server, it does not appear in the corresponding folder when I download the reports. This behavior seems unusual, especially since the subreport exists on the server at that location.

Note:- The subreport im suppose to embed uses BAQ as datasource

1 Like
7
1 Like
8

You cannot do this. I you want to use a baq, then you have to start over from scratch and build a baq report.

Yes it is, if you follow the steps. You do not upload anything directly to the report server, you upload via report style as I explained.

2 Likes
9

Sad to hear this.

Thanks for response

2 Likes