Report Data Definition in Epicor lets you create BAQ Reports and link multiple tables, BAQ is powerful enough to recurse 100 levels if done right in less than 20 seconds.
Overall the Report Data Definition Designer, still isnt crazy powerful for mixing out-of-the-box RDD and BAQs… But what you are asking has been done and can be done with the tools available.
In 10 years, I have NEVER done a SQL View or Stored Procedure, It is much easier to do so, but working within the toolchain always worked.
Worst case you write out the data to CSV from BAQs and have Powershell do some reporting, but I havent hit that complexity yet either.
On another note I was told by Epicor CAM that they now offer a Readonly Database with SQL Access for on-prem to read their data. I never asked for additional info.
I think @JeffLeBert at one point had a vision that every RDD would just become a BAQ in a few years and eliminate the old RDD ways… but they do run alot of Server-Side Internal .dll logic, that is not always easy to replicate in BAQ.
My “vision” was that new reports would be written using BAQs.
Electronic Interfaces was the primary way of adding custom code to a report when using BAQs. @klincecum, good point about using UBAQ instead. I haven’t played with the combination of UBAQ and BAQ reports.
