This is best Fabric, Power BI, SQL and AI community event. How do we know? The last event sold out! Save €200 with code FABCMTY200.
Register nowA new Data Days event is coming soon! This time we’re going bigger than ever. Fabric, Power BI, SQL, AI and more. Don't miss out.
Hi Community,
I am facing an issue with the Azure Map visual in Power BI where numeric field values are being automatically aggregated (summed), even though the data is at the job level (i.e., every entry/row is unique per job).
The Problem: When I plot multiple job locations on the map and display a numeric field (e.g., Market Value), the visual sums up the values instead of showing the individual value for each job. This is incorrect behavior since each job already has a unique record.
What I Have Already Tried:
Expected Behavior: Each pin/bubble on the map should display its own individual job-level value, not an aggregated sum of all visible jobs.
Has anyone faced this issue or found a workaround? Any help would be greatly appreciated.
Thank you!
Hi @Vaibhav_99,
Have you had a chance to review the solution we shared by @MFelix @trivedisunita ? If the issue persists, feel free to reply so we can help further.
Thank you.
Hi @Vaibhav_99 ,
The Azure Map visual is aggregating because it groups by location, not job ID.
Azure Map visual groups data points by geographic coordinates. If more than one job exists at the same location, the numeric field is aggregated even if you set “None,” the visual still requires an aggregation when multiple rows map to the same point.To fix this, add Job ID (or another unique field) to the legend or tooltip so each job’s value is displayed individually.
Also Keep Market Value aggregated but add Job ID and Market Value to the Tooltip. This way, hovering over a bubble shows each job’s value. change the aggregation from sum to average.
Hope this helps!
Thank you
.
Hi @Vaibhav_99 ,
When you refer that the information is individual at each job do you mean each job location, or a location can have multiple jobs?
I'm asking this because if you only have one job per location the sum of the values is the same has that row so the aggregation is in fact a single value, however if you have more than one job per location then this is the expected behaviour since the map is aggregating the information at values level because you cannot have details.
Having more than one value then you need to turn place values on the legend so you can get the details inside each job location.
Regards
Miguel Félix
Proud to be a Super User!
Check out my blog: Power BI em PortuguêsCheck out the May 2026 Power BI update to learn about new features.
Sign up to receive a private message when registration opens and key events begin.
If you have recently started exploring Fabric, we'd love to hear how it's going. Your feedback can help with product improvements.
| User | Count |
|---|---|
| 32 | |
| 25 | |
| 23 | |
| 22 | |
| 13 |
| User | Count |
|---|---|
| 61 | |
| 47 | |
| 27 | |
| 24 | |
| 19 |