Forum Discussion
Resolver IIMap visual mark the wrong position for Cities outside USA
The Bing Maps team is forcing a two-fold change for Power BI; they are deprecated the Bing Maps v8 Control, and are also switching to a new geocoder. Please refer to https://powerbi.microsoft.com/en-us/blog/power-bi-desktop-june-feature-summary/#maps.
If you are using comma separated strings as a workaround to the earlier geocoder limitations, you should change to use a hierarchy. In this case, create a column called "Country", set data category to Country / Region, and add it above the State and City in the hierarchy. Then Drill Down via Hierarchy Drill (fork icon). Or you can use a City column directly as following screenshot. Please notice that there is no comma, Country for the values in City column.
Users with comma separated concatenated values may see breaks, changing Data Category of this column to Place should work, and it is actually be design.
Best Regards,
Herbert
Microsoft Employee
The Bing Maps team is forcing a two-fold change for Power BI; they are deprecated the Bing Maps v8 Control, and are also switching to a new geocoder. Please refer to https://powerbi.microsoft.com/en-us/blog/power-bi-desktop-june-feature-summary/#maps.
If you are using comma separated strings as a workaround to the earlier geocoder limitations, you should change to use a hierarchy. In this case, create a column called "Country", set data category to Country / Region, and add it above the State and City in the hierarchy. Then Drill Down via Hierarchy Drill (fork icon). Or you can use a City column directly as following screenshot. Please notice that there is no comma, Country for the values in City column.
Users with comma separated concatenated values may see breaks, changing Data Category of this column to Place should work, and it is actually be design.
Best Regards,
Herbert
Resolver IIHello v-haibl-msft, thank you for this explanation. I just changed my dimensions ETL, created this hierarchy and everything is working very well!