Datasets aren't always textbook examples of information engineering. Many times, they are filled with duplicate keys, data and just plain garbage. As PBi developers we don't have the option of fixing the data and can only deal with it. Both the Table and the Matrix visuals have an annoying feature of hiding data. For instance, while this table has thousands of instances of this Event, only one is shown, despite the option "Don't Summarize" being checked : Add more details and more rows show up. Nice feature. But in order to see all the instances, you sometimes have to add so many columns that the table becomes large and unreadable. Nobody like scrolling a table to the right to see all the data. Likewise, the Matrix will also hide data, collapse, and remove duplicates. This forces you to add a GUID, Row_ID, etc in the Transform step to provide a unique ID for each row, which then has to appear in the Row of the Matrix setting, which then appears in the Matrix hierarchy, or in the Table, which the user has no clue what it means. We need a second set of Table and Matrix visuals that show the data as it is, or, provide a way to turn off automatic aggregating.
... View more