Join us at FabCon Atlanta from March 16 - 20, 2026, for the ultimate Fabric, Power BI, AI and SQL community-led event. Save $200 with code FABCOMM.
Register now!The Power BI Data Visualization World Championships is back! Get ahead of the game and start preparing now! Learn more
Hello,
I'm reading data from Hubspot in PowerBI (through API calls) and I run into an issue where the results are different between Desktop and Web versions. Here's the scenario:
So it looks to me as if after the publish one of relationships changes to sort of outerjoin or 1:n type (the raw numbers are fine both in Desktop and App) and blows up to infinity.
Has anyone seen this behavior? If so - anything to do about it, apart from contacting the Support?
Best,
Bart
Solved! Go to Solution.
For those of you wondering what was the root cause - in some cases Hubspot returns (through API call) non-int numbers with infinite small precision, which throws off the Web version of PowerBI (Desktop handles this well). For example this is Deal Stage Probability of 50%:
Not much that can be done about itexcpt maybe converting the number to String, truncating it to 2 chars and converting again to Decimal.
For those of you wondering what was the root cause - in some cases Hubspot returns (through API call) non-int numbers with infinite small precision, which throws off the Web version of PowerBI (Desktop handles this well). For example this is Deal Stage Probability of 50%:
Not much that can be done about itexcpt maybe converting the number to String, truncating it to 2 chars and converting again to Decimal.
Hi @BartekStr ,
If you refresh the data in Power BI Service when the data is abnormal, do you still get the wrong data?
Best Regards
Lucien
Yes, unfortunately so..
The Power BI Data Visualization World Championships is back! Get ahead of the game and start preparing now!
| User | Count |
|---|---|
| 56 | |
| 55 | |
| 31 | |
| 18 | |
| 14 |