Data Bug when summarizing with nulls

[Anonymous]

I've got an odd bug I believe. My data looks like this:

If I put that into a table with no summarizing, it looks as above.

When I put Budget/Forecast as Summarize and hours as don't summarize, I only get Budget/Forecast, Hours is blank. When I do the oposite, set Budget/Forecast as don't summarize and Hours as summarize, I get hours with blanks for Budget/Forecast. 

 

Setting the nulls to 0 fixes the issue, but why is the system doing that? It is throwing data away, which feels like a bug to me. 

[Greg_Deckler]

Not sure I would call that a bug. It's an issue around the visuals trying to prune out unnecessary data and only focus on what is important so technically it is by design. When you are summarizing on one or the other, you are getting nulls back for that summarization. When the visuals see this, they throw out those rows because it assumes that they are worthless, no data. So, when you summarize by budget/forecast it throws out the null rows where you have hours and vice versa. It's a visualization optimization thing that just doesn't pan out in your specific circumstance.

[Anonymous]

I would agree if all values shown were null, but if I have data to display (a non-null row) it should show irregardless of if the sum column is null or not.

Frankly, if that's by purposeful design, it's a poor design. Not showing data is very confusing for the user (it took me a while of troubleshooting to figure out why I wasn't seeing those records as expected), and potentially dangerous from a BI perspective (missing data can lead to thinking there is no data and bad decisions). 

[v-yulgu-msft]

Hi @Anonymous,

You could enable the "Show items with no data" option for those unsummarized fields.

Best regards,

Yuliana Gu