Forum Discussion
Design advice needed
Hm, why do you want millions of records in a table visualiization?
Have you tried visualizations that aggregate the data, like bar charts?
Our financial crime have asked for a tabular output, showing each transaction in the 1 Half of 2015. I have emailed them asking them to reconsider their requirements because even SSRS would struggle with the vast number of rows.
Being new to Power BI / Excel Data Models, I would like to understand the optimaldesign aproaches to use.
So far, I have picked up from the previous replies to my quesiton (thanks everyone):
- Use Direct Query (as opposed to import)
- Group/Aggregate the data (as opposed to large number of "atomic" rows)
Are there are any other important deisgn principles to follow?
amir_tohidi Another option is to show aggregated visuals, (giving actual value to see things) and if they want to look at the data - have them use the "Export Data". Worth seeing if this works in the Service, that way, if they want to sit and wait for the records to load, they can.
Best case I would think is to meet them half way, set up visuals that are meaningful, slice them down to smaller chunks, and then they can export smaller pieces. Regardless of what anyone says, a report with a million rows is meaningless, there is no way they are looking at it all. If they take that and filter it down, then have them do that prior to exporting it from Power BI... Another option would be for them to Analyze in Excel off a report if they want to get more granular. (just some thoughts).
Thanks Eno1978. I will discuss the various options with the users and update the thread in due couse with how we decided to overcome the issue.
