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 am encountering an issue that seems to be a bug talked about here before, but I have not seen a solution to it.
I am using the Azure Maps, plotting points with a County, State identifier and I want to use the "Use size as weight" option for my heat map. I have a numerical column in place for Size, but when I toggle on "Use size as weight" all my points disappear. I can use this point just fine as a weight on the "bubble map" option, just not in heat map.
I have seen other threads on this like : https://community.fabric.microsoft.com/t5/Desktop/Azure-Maps-Heat-Map-Size-Field-Not-Working/td-p/42...
But so far I have no seen someone offer a solution that fixes the issue. Is this just a known bug? Has anyone found a work around?
Thanks
Solved! Go to Solution.
Hi @grayscg
The "Use size as weight" option is working for me , but I had to keep bubble layer option enable to make it work & did some setting changes on bubble layer and heat map
Hi @grayscg ,
Thank you @kushanNa, for your reply regrading the Issue
Thank you for reaching out to the Microsoft fabric community forum.
I have tested this in the latest Power BI build. Although the old “Use size as weight” switch has disappeared, the same logic applies when you drop your numeric field into the Bubble size bucket and turn on the Heat map layer. The quickest way is to create a text column that joins County and State use that in Location, put your measure in Bubble size, switch on both Bubble and Heat map in the Format pane, and set the bubble transparency to 100 percent if you want the bubbles hidden. With this setup, the map treats the numbers as weights, and the bright “hot” spots scale exactly to your values.
please find attached screenshot and pbix for your reference:
If this answer was helpful and pointed you in the right direction, please consider clicking "Accept as solution" and kindly upvote it may benefit other community members reading this thread. If you have any further questions, feel free to let us know.
Best Regards,
Harshitha.
Community Support Team
Hi @grayscg ,
Thank you @kushanNa, for your reply regrading the Issue
Thank you for reaching out to the Microsoft fabric community forum.
I have tested this in the latest Power BI build. Although the old “Use size as weight” switch has disappeared, the same logic applies when you drop your numeric field into the Bubble size bucket and turn on the Heat map layer. The quickest way is to create a text column that joins County and State use that in Location, put your measure in Bubble size, switch on both Bubble and Heat map in the Format pane, and set the bubble transparency to 100 percent if you want the bubbles hidden. With this setup, the map treats the numbers as weights, and the bright “hot” spots scale exactly to your values.
please find attached screenshot and pbix for your reference:
If this answer was helpful and pointed you in the right direction, please consider clicking "Accept as solution" and kindly upvote it may benefit other community members reading this thread. If you have any further questions, feel free to let us know.
Best Regards,
Harshitha.
Community Support Team
Ah I knew it would be some workaround like this, very Power BI lol. Thank you so much!
Hi @grayscg,
Just wanted to check if you had the opportunity to review the suggestion provided?
If the response has addressed your query, please Accept it as a solution and give a 'Kudos' so other members can easily find it.
Thank You,
Harshitha.
Hi @grayscg
The "Use size as weight" option is working for me , but I had to keep bubble layer option enable to make it work & did some setting changes on bubble layer and heat map
Thank you!
The Power BI Data Visualization World Championships is back! Get ahead of the game and start preparing now!
| User | Count |
|---|---|
| 37 | |
| 37 | |
| 33 | |
| 32 | |
| 29 |
| User | Count |
|---|---|
| 130 | |
| 88 | |
| 82 | |
| 68 | |
| 64 |