Hi,I am building simple column chart which represents sold items by stores. We have 171 stores. I supposed to get 171 columns to see sales of every single store. After creation there is yellow triangle with exclamation mark in the upper left corner of the chart. After clicking on it I see this Message: Why do I get this error? I mean 171 is quite normaln as you have slider at the bottom of the chart. Yes I can filter stores by some category. But on the top level, ct wants to see all the stores as you can see in excel pivot table not saying you can do it in any other visualization tool such as Datawatch, Qlikview... PowerBI should handle it.Is there any limitation on the columns, chart can presents?

This is becoming a large problem as we roll out PowerBI.Com in my firm. This error is causing a trust issue with my users. Using the same Tabular models, same data, same filters - they never got this error in SharePoint PowerView. Note my example. The error says that "too many month-year" values... But, it's filtered for 2015. It can't possibly be too many months for one chart. Data has been removed from this visual - it's essentialy lying at this point. Though, oddly enough it's the legend-value that is the problem. I hope this is being fixed. It's becoming a big issue for my users that are PowerView pros wanting to make the transition to PowerBI.com.

WillT wrote on 12-22-2015: "We're aware that there are problems with some sparse datasets, and are working to fix it." It is now July 25, 2018, more than three years later, and I'm still running into this "Too many values" limitation. Please fix it.

I counted columns manually and it is exactly 121 from 171 columns. Yes I can order them ascending and then descending and see both outline values, but I want to figure out how to get the full picture.All the caharts are created in PowerBI desktop version.

I would suggest, if possible, to pivot your data so that stores are in rows and your metrics are in columns. Then you should not run into this.

What in a case, it is not possible or I do not want to?

Too many values | Microsoft Fabric Community

16 Replies

Greg_Deckler
Community Champion
11 years ago
I would suggest, if possible, to pivot your data so that stores are in rows and your metrics are in columns. Then you should not run into this.
- mstefancik
  Advocate IV
  11 years ago
  What in a case, it is not possible or I do not want to?
  - Sean
    Community Champion
    11 years ago
    171 Columns in a Column chart is not a problem at all - you should just have to scroll to the right to see all
    
    Can you list all relevant columns you have in the table you use for the column chart?
    
    Something like => Store#, Sales, Etc... => And tell us which do you use to build the chart?
    
    I actually get a similar message in a pie chart when few slices are simply too small compared to the rest to show their data labels!
getthedata
New Member
10 years ago
Bump bump

Hello Power BI team, can I get some clarification what this message really means?

Some people report that it is only an issue on the desktop tool and uploading report to PowerBI site resolves. However, that doesn't work for me.

Others as in this thread above suggest data should be transformed into groups in order for PowerBI to be able to present it. Frankly this is not something that I expect is a requirement. I experience the "Too many values" message with record sets that are not what would be considered "too big" on any other BI solution including Excel pivot tables, Power Pivot, etc.

I am using latest PowerBI desktop tool and a license free PowerBI with my Office365 E3 account.

What is really happening here?

* is it a Desktop tool limitation?
* is it something that happens in specific situations?
* is it a free PowerBI account limitation?
* is PowerBI just a limited capability BI solution?
* is this something that will be resolved or upgraded in future?

I really like what i see witih Power BI so far but this is a severe limitation for a modern BI solution.

Thanks.

Looking forward to your reply!!
- LetBloodline
  Advocate I
  10 years ago
  It's a chore but it happens even if you have some data too small to be rendered
  
  dato1 quantità
  a 1000000
  b 900000000
  c 1
  
  Try put that on a pie and the yellow signal appears. But "too many values" is a misleading information. And i can be OK with not be able to see c's slice. I'd really like to be able to remove that warning
- WillT
  Community Admin
  10 years ago
  Hi everyone. You're running into data point limits that exist to make sure performance isn't impacted. We're aware that there are problems with some sparse datasets, and are working to fix it. We plan to get to a point where you can load charts with many more datapoints, even millions in many cases. Stay tuned for updates in the new year where we'll start to ship improvements to this. Thanks for you patience!
  - RichardL
    Microsoft Employee
    8 years ago
    WillT wrote on 12-22-2015: "We're aware that there are problems with some sparse datasets, and are working to fix it."
    
    It is now July 25, 2018, more than three years later, and I'm still running into this "Too many values" limitation. Please fix it.

ronkochanowski

Frequent Visitor

8 years ago

I'd like to chime in on this topic as well. For me it doesn't appear to be an issue with a visual, but with the data itself. I have a a one-to-many join between a DateDimension table and HeadCounts table, as well as a Contributions table. DateDimension contains columns for FiscalYear:

FiscalYear = CONCATENATE("FY-", IF(MONTH(DateDimension[DateKey])<=8,VALUE(FORMAT(DateDimension[DateKey], "YYYY")),VALUE(FORMAT(DateDimension[DateKey],"YYYY"))+1))

And FiscalMonth:

FiscalMonth = 
SWITCH (
    TRUE(),
    MONTH(DATEVALUE(DateDimension[DateKey])) = 1, "05-Jan",
    MONTH(DATEVALUE(DateDimension[DateKey])) = 2, "06-Feb",
    MONTH(DATEVALUE(DateDimension[DateKey])) = 3, "07-Mar",
    MONTH(DATEVALUE(DateDimension[DateKey])) = 4, "08-Apr",
    MONTH(DATEVALUE(DateDimension[DateKey])) = 5, "09-May",
    MONTH(DATEVALUE(DateDimension[DateKey])) = 6, "10-Jun",
    MONTH(DATEVALUE(DateDimension[DateKey])) = 7, "11-Jul",
    MONTH(DATEVALUE(DateDimension[DateKey])) = 8, "12-Aug",
    MONTH(DATEVALUE(DateDimension[DateKey])) = 9, "01-Sep",
    MONTH(DATEVALUE(DateDimension[DateKey])) = 10, "02-Oct",
    MONTH(DATEVALUE(DateDimension[DateKey])) = 11, "03-Nov",
    MONTH(DATEVALUE(DateDimension[DateKey])) = 12, "04-Dec")

At one point the error was indicating that PowerBI couldn't perform the function on varchar data types, so I added the DateValue function to the formula...to no avail.

Fiscal columns displaying blanks

Overall, there are over 800K records, but only approximately 1,000 that are not displaying the Fiscal info...the remaining rows display the info as desired.

Here's the error associated with the above table:

Any positive input towards a solution is greatly appreciated!

Ron

Forum Discussion

Too many values

16 Replies

Related content

Closing value

remove duplicate value within a row

IF Negative value

DAX for calculating retroactive values

Handling Null Values

dato1	quantità
a	1000000
b	900000000
c	1