You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The problem I'm facing is that when I try to aggregate the measure from the Sensis table (not the base store)
I can´t aggregate the measure sensitivity to every hierarchy from the base store (not even by the fields used to join both tables).
However, the measure called PL.SUM has the functionality to be aggregable by every hierarchy.
What we would like to know is if there is any method or attribute for measures from other stores (that are not the base store) to
have the functionality to be aggregable by any base store hierarchy, just like PL.SUM.
I know it is possible to create a new measure that aggregates the original measure to a certain hierarchy, but it is not efficient to
be creatinga measure every time I want to aggregate the measure to a different hierarchy, as it happens with measures from the
base store, they can be aggregable without creating new measures.
The tt.value function creates a measure representing the value of the column, it doesn't provide any information on how to aggregate it. The value function propagates the value of the column through levels as long as it stays the same (see the documentation for a more detailed example. In the screenshot you shared, since all the sensitivity values are different, without information on how to aggregate it there is no value to display using only the as_of_date and country levels, therefore the value is None and the column in the pivot table is not displayed since it contains no data.
You can use any of the functions in the tt.agg module to create aggregated measures.
For example, if you want the sum of your sensitivities you can use tt.agg.sum(sensis_store["sensitivity"])
Wi1iku
changed the title
Measures in base table do not aggre
Measures in joined table do not aggregate
Aug 5, 2022
Issue
The problem I'm facing is that when I try to aggregate the measure from the Sensis table (not the base store)
I can´t aggregate the measure sensitivity to every hierarchy from the base store (not even by the fields used to join both tables).
However, the measure called PL.SUM has the functionality to be aggregable by every hierarchy.
What we would like to know is if there is any method or attribute for measures from other stores (that are not the base store) to
have the functionality to be aggregable by any base store hierarchy, just like PL.SUM.
I know it is possible to create a new measure that aggregates the original measure to a certain hierarchy, but it is not efficient to
be creatinga measure every time I want to aggregate the measure to a different hierarchy, as it happens with measures from the
base store, they can be aggregable without creating new measures.
Thank you very much!
Steps to reproduce
Code
Whole notebook code
Actual Result
Does not aggregate measures automaticly
Expected Result
When not aggregating from sensis tables, measures are created
Environment
Logs (if relevant)
Aditional Data
The text was updated successfully, but these errors were encountered: