"Too many values" calculation is incorrect when adding a legend.

Question

I have a chart that has every mniute of the day along the x axis. This works great in Power BI desktop and the Web.

When adding a series that is wholely dependant on the x axis (i.e. daypart against minute of the day - there can only ever be one value), Power BI complians that there are now too many rows, even though the number of rows has not changed, as far as the dataset is concerned, there is only one additional column.

In my example below, I have minute of the day coloured by the hour of the day. Every minute can only exist in a single hour of the day, and yet this is produced more rows.

v-jiascu-msft · Answer

Hi&nbsp;neilp1,&nbsp;There are too many values indeed though they are blanks. You can see how the legend works from the following picture.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;We still can show the data of your visual.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;What would you like to do exactly? Maybe there is better solution.&nbsp;Best Regards!Dale

neilp1 · Answer

I'm not sure I understand. Could you explain exactly how there are too many values? The number of rows is the same!

It sounds like PowerBI is being over protective here - the number of possible rows is higher, but the error is showing even though the number of actual rows is within the allowed limit.

v-jiascu-msft · Answer

Hi&nbsp;neilp1,&nbsp;Let's go on this example. There are only three rows at the start. But when the Color legend is added in, the rows turn to every Color multiply every year. That's why there are many many records.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Best Regards!Dale&nbsp;&nbsp;

neilp1 · Answer

Hi Dale,&nbsp;I understand that in your example, although in your example your source data has more rows than the 3. In my example, all the source rows are displayed in the first example, so there are no more possible rows.&nbsp;It seems that power bi limits the data based on the possible values, not the actual number of rows in the source dataset.&nbsp;if I chart x by a legend of y - Power BI will tell me there are 50 possible rows (10x5), whereas the source data only actually has 10?. Is that correct?x,y1,a2,a3,b4,b5,b6,b7,c8,d9,b10,e&nbsp;If so, can this behavour be changed so that it will chart the 10 rows because it never really has 50? My point it that the limit is being applied too agressively when it is assuming more rows than really exist in the data.

v-jiascu-msft · Answer

Hi&nbsp;neilp1,&nbsp;I'm afraid this is how legend works. But if you share the expected result you want, maybe we can find the proper solution.&nbsp;Best Regards!Dale

Forum Discussion

"Too many values" calculation is incorrect when adding a legend.

6 Replies

Related content

"Too Many Values" in stacked bar chart

How to fix "Too Many Values" for Matrix

(Confirmed not possible)Stacked Bar Single Colour for All Legend Categories avoid "Too many values"

Snowflake connector: "We cannot convert the value null to type Text"

Detecting "Too many values" condition