Forum Discussion
Azure Maps – Reference Layer Fails to Render Without Field Swap
Hi darrylit,
Thank you for reaching out to the Microsoft Fabric Forum Community.
This behavior is a bug in how Power BI links the visual fields to the underlying rendering engine. The reference layer seems to require the Location field to match its key (e.g., MESH250MID) at load time, even if it should be independent of the bubble layer.
Power BI is grouping bubbles by the Location field first (MESH ID), and then only retaining one per group ignoring the legend unless Location is more granular.
Azure Maps reference layers (shapefiles or GeoJSON) support only static formatting. Dynamic formatting is not supported for uploaded shape files even if tied to a slicer or measure.
You may find this related community discussion helpful:
Kind regards,
Prasanna Kumar
Hi darrylit,
Thank you for reaching out to the Microsoft Fabric Forum Community.
This behavior is a bug in how Power BI links the visual fields to the underlying rendering engine. The reference layer seems to require the Location field to match its key (e.g., MESH250MID) at load time, even if it should be independent of the bubble layer.
Power BI is grouping bubbles by the Location field first (MESH ID), and then only retaining one per group ignoring the legend unless Location is more granular.
Azure Maps reference layers (shapefiles or GeoJSON) support only static formatting. Dynamic formatting is not supported for uploaded shape files even if tied to a slicer or measure.
You may find this related community discussion helpful:
Kind regards,
Prasanna Kumar