Hi,
Just checking to see if anyone's got a better solution to an additional reporting requirement that's been requested. We have a project dimension that lists (surprise, surprise) projects. There are some additional attributes that will be attached to those projects such as sector and location. The request is to report summaries based on those attributes, effectively treating them as quasi-dimensions.
I can already create activeforms that filter with MDX to get a subset based on an attribute, but can't quite see how to get a table like report of all attribute values.
So far I've considered creating single dynamic subsets based on the attributes and using those in the DBRWs, or using a TI to create another consolidation hierarchy on the dimension and report off that hierarchy.
Anyone have any other cunning plans for this situation?
Cheers,
Mike
Reporting - Summing by attribute?
- gtonkin
- MVP
- Posts: 1265
- Joined: Thu May 06, 2010 3:03 pm
- OLAP Product: TM1
- Version: Latest and greatest
- Excel Version: Office 365 64-bit
- Location: JHB, South Africa
- Contact:
Re: Reporting - Summing by attribute?
Why not creating a Reporting hierarchy in you Projects Dimension?
Create a Total with children based on the unique list of attributes then assign each project to its parent in this hierarchy using TI. Just remember to flatten and rebuild this hierarchy as and when required.
The only issue with this approach is frequent changes to the attributes.
In the alternative, create the various subsets using MDX, name appropriately then reference the subset name in your DBRW to bring back the total.
The drawbacks here are lots of subsets and having to create additional ones if a new attribute is added.
I would generally go with the first option as TI can rebuild as and when required reducing manual intervention.
Create a Total with children based on the unique list of attributes then assign each project to its parent in this hierarchy using TI. Just remember to flatten and rebuild this hierarchy as and when required.
The only issue with this approach is frequent changes to the attributes.
In the alternative, create the various subsets using MDX, name appropriately then reference the subset name in your DBRW to bring back the total.
The drawbacks here are lots of subsets and having to create additional ones if a new attribute is added.
I would generally go with the first option as TI can rebuild as and when required reducing manual intervention.
-
- MVP
- Posts: 3240
- Joined: Mon Dec 29, 2008 6:26 pm
- OLAP Product: TM1, Jedox
- Version: PAL 2.1.5
- Excel Version: Microsoft 365
- Location: Brussels, Belgium
- Contact:
Re: Reporting - Summing by attribute?
You could also add the attributes as dimensions (your "quasi-dimensions"), in the same cube or a reporting cube.
This could be useful if users want to be able to change attributes but do not want to change historical data when the attribute was different.
This could be useful if users want to be able to change attributes but do not want to change historical data when the attribute was different.
Best regards,
Wim Gielis
IBM Champion 2024-2025
Excel Most Valuable Professional, 2011-2014
https://www.wimgielis.com ==> 121 TM1 articles and a lot of custom code
Newest blog article: Deleting elements quickly
Wim Gielis
IBM Champion 2024-2025
Excel Most Valuable Professional, 2011-2014
https://www.wimgielis.com ==> 121 TM1 articles and a lot of custom code
Newest blog article: Deleting elements quickly