Forum Discussion
Pre-Aggregated Data
Would it be sufficient for what you're doing to use measures that report based on the count of your surveys? It doesn't solve the overall question of importing aggregated vs non-aggregated data, but maybe it will help for the particular example you used.
If you've got a measure that caculates the number of responses you have:
ResponseCount = DISTINCTCOUNT(ResponseTable[ResponseID])
You could use that as a buffer for what you report. If you want an average of the response scores for question 1 on your survey, you could use:
Q1Avg = IF([ResponseCount] < 10, BLANK(), AVERAGE(ResponseTable[Q1]))
That will still show your rollup scores and allow you to use the drill-down features nicely, and any stores (or any level of your hierarchy, really) that have fewer than 10 responses will show up on your chart axis, but won't show any scores for that level.
Any other idea on this one folks?
Unlike the OP, I'm utilizing economic data from the bureau of economic analysis and bureau of labor statistics, which only comes pre-aggregated, so I don't have the option of setting up a rule on when to show the data.
Also, some of the sub-components of over-arching sectors are suppressed, so I can't just sum up across sub-pieces to get the whole.
What I really need is a drill down to actually work like a filter, so it filters down to Category = "Subsector" when I drill down, and when I drill back up, it needs to filter on Category = "Sector". Sector != sum(Subsector) because some subsectors are suppressed to protect confidentiality, so it seems like only filtering would work, but I don't want people to have to change the slicer back and forth every time they drill up or down.
jordanlevine, could you find any solution to your problem? I'm having a similar problem here where most of my aggregated calculations come from a statistical model and stored on a database. My report needs to be able to access information both from top and bottom of my hierarchy without any calculation.