Forum Discussion
County-level data not segregating properly in Map visual on Power BI Desktop, but works on Power BI
Hi SehulRanbhor ,
Just wanted to check if the solution provided has met your needs. If yes, Please consider marking it as "Accepted Solution" to assist others with similar queries. If further assistance is needed, please reach out.
Thank you.
Hi v-veshwara-msft Thanks for response .
None of this approach work still finding the solution.
- v-veshwara-msft1 year ago
Community Support
Hi SehulRanbhor ,
Thanks for confirming. Since the issue still persists even after trying the above steps, here are a couple of additional suggestions to help narrow it down:
Could you please confirm whether you're using only County or ZIP in the Location field of the map visual? If so, try removing them and use only the combined County_State column.
Also, just to rule out any cached behavior - after updating the field and setting the data category, try saving the file, closing Power BI Desktop, reopening it, and checking again.
Additionally, based on similar reported cases, you can try creating another column that includes the country for better accuracy:
County_State_Country = [County] & ", " & [State] & ", United States"
Then set the data category of this column to Place and use it as the Location in your map visual. This gives Bing Maps more context and often resolves unexpected placements.Similar thread: MAP showing wrong locations when using counties - Microsoft Fabric Community
Please refer to this link for Tips regarding Map visuals: Tips and Tricks for maps (including Bing Maps integration) - Power BI | Microsoft Learn
If possible, please share a sample pbix file, or a sample of your dataset (with any sensitive info removed), or a screenshot of the fields used in the map visual. I’ll try to reproduce the exact setup and check further.
Hope this helps. Please reach out for further assistance.
If this post helps, then please consider to Accept as the solution to help the other members find it more quickly.
Thank you.