Hi Andrew,

With the Hierarchical Data feature in Reporting 12.2 you can achieve what you want. You need to load the data into a data structure with the hierarchy you want to display in the report. That hierarchy can have any number of nested levels (e.g. a parent with 3 children, which 3 children each one). Once you add a data source bound to that class, you can drop it in the design surface and you'll get the report you'd expect.

I hope it helps,

Andres.

The suggestion that joining data into one larger data set, then using hierarchies to essentially unjoin data seems extremely short sighted.  Sub reports are useful when you have a report header at one level and multiple detail records that are all direct foreign keys to one header.  Joining this into a hierarchy and attempting to present it in a user consumable fashion seems backwards.  A simple example may be taken as a relationship between a Team-Player-Office Staff-Fans-Alumni, with Team as the head, you could have details sub reports in 4 quadrants of the 1 level sibling records.  Joining this data is easy, but it is a 2 level hierarchy with 5 entities, essentially the application of sub reports for the past 25 years?

I'm confused how this is thought of as a work around?

My last post was 10/18, now 10/26. What's the status with me getting Reporting 12.2?

Definitely, yes! Is that the version that's being released in November?

Hi,

Reporting 12.2 is planned to be released mid-November. You will be able to install it as part of your Ultimate 12.2 subscription once it is released.

If you want to have an early version before the release, please let me know.

Best,

Leo