Data Dump - Too large for Cube View
Hi All,
I was hoping to brainstorm a solution to a problem. Our auditors have requested a mapping of base-level data to the aggregated, financial statement line item data that appears in our financ...
Forum Discussion
After trying different solutions, I think the problem is less the volume of data and more that we have 3 different "base" cubes that then aggregate into our Company-wide cube; essentially data from 3 ERPs gets loaded into a separate cube, and then those 3 cubes are merged into our Company cube. When I run the TBs in the base cubes they populate quickly, but that still leaves the problem of not having visibility into the aggregate cube.
I'll likely make 3 base TBs then have a book that runs each base TB as a tab that can then be aggregated; at least this way we'll only have 3 files to copy+paste, rather than 200+.
This is our exact setup, 3 base cubes that correspond to different divisions with 1 top level reporting cube. We can simply do A#IncomeStatement.Tree (or .Base) with any entity from the hierarchy. Edit: we have different base accounts for the divisions, and through extensibility the Base member expansion will resolve to the appropriate base accounts based on the entity selected.
Can you confirm that extensibility was implemented for cube, entity, and account?