Check your eligibility for this 50% exam voucher offer and join us for free live learning sessions to get prepared for Exam DP-700.
Get StartedDon't miss out! 2025 Microsoft Fabric Community Conference, March 31 - April 2, Las Vegas, Nevada. Use code MSCUST for a $150 discount. Prices go up February 11th. Register now.
Hello,
I recently tried to create a histogram in Power BI from some data that ranged between 0 and 0.140. I right clicked the data and created a a new group. I selected Group Type to be "bin" and specified a size I wanted. I clicked OK. So, far things seemed fine. The binned data appeared on my Fields section. However, whenever I tried to use this binned data in a table or graph, I always saw this error:
OLE DB or ODBC error: [Expression.Error] We couldn't fold the expression to the data source.
Through many struggles and experiments, I finally came to to believe that the problem is related to trying to bin data with floating point values. I cooked up this work around.
1. Duplicate the column of data.
2. Multiply that column by 1000
3. Duplicate that scaled column of data
4. Round the scaled data to the nearest whole number
5. Create bins on this scaled and rounded data
6. Create a histogram of the scaled data on the Y axis and the bins of the scaled and rounded data on the X axis
This works but I was curious to ask if I have discovered a bug in the software or there is some other way to solve this problem. I am in DirectQuery mode to a Kusto database. Not sure if that is relevant.
Solved! Go to Solution.
It turns out to be a problem in the Kusto connector. Fixes are planned. One work around is to bin it in the query. This works today.
I cannot recreate this. Seems to work for me. I am on the December 2019 version of Power BI. See attached.
Thanks for trying. Not sure what the difference is. My guess would be that you are not using Direct Query and a Kusto connection. I checked my version and found this:
Version: 2.76.5678.782 64-bit (December 2019)
I will also mention that 2 other people I know tried and also reproduced the same error. So, it wasn't just me.
Yep, I'm just using Import with an Enter Data query so my suspicion would be that this is some kind of problem with DirectQuery.
It turns out to be a problem in the Kusto connector. Fixes are planned. One work around is to bin it in the query. This works today.
March 31 - April 2, 2025, in Las Vegas, Nevada. Use code MSCUST for a $150 discount!
Arun Ulag shares exciting details about the Microsoft Fabric Conference 2025, which will be held in Las Vegas, NV.
User | Count |
---|---|
119 | |
78 | |
58 | |
52 | |
46 |
User | Count |
---|---|
170 | |
117 | |
63 | |
58 | |
51 |