Comment on page
Tables are included in all dashboards to enable users have more than one way to access data. Format your tables with the user in mind, making all data easy to access and understand.
They should have a 0 or explain they are missing. Blank cells are confusing and unclear.
Power BI tip: To force a zero to appear add a “+ 0” to your measure. Sum of Sales = Sum(Sales[SalesAmt]) + 0
This may vary based on your data. For tables showing data over time (so each row is a date or month), sort the table to have the newest or most recent values at the top. Recent data is likely most relevant for your users.
A table below a map should be sorted by the measure or variable that is shown in the map. For example, a table below a choropleth map showing population density should sort the table by population density.
If your table includes dates, they should always be rows (each date is a row). In many cases, your table will match your cleaned data structure.
While “wide” data can be more intuitive for users, sometimes a wide table is difficult to use. Therefore, long data is acceptable if the wide table doesn't fit within the template. For example, while this wide table of data by race may be intuitive, the long version is also acceptable because the wide format may not fit on most dashboards.
A wide table with each row as a date and each column as a different race or ethnicity category.
A long table with each row being a month and race category combination. While less intuitive, this may be necessary because of space limitations.
Data bars within tables are typically difficult to ensure visibility for most users.
If you do implement data bars, you will need to check the color contrast to ensure that the bar contrasts sufficiently with the background, and the data label contrasts sufficiently with the bar. This is difficult to do well.