Forum Discussion
Filed Azure map - Only Render if a Slicer is Set
- 3 months ago
It is frustrating, yes. Ultimately, my solution was to aggregate the data at the table level in power query, use no measures and apply the table fields directly to the map visual... not ideal, but it works now.
Hi Moehimby,
Thank you for sharing the workaround you used.
Your insight into how Azure Maps handles very large datasets with explicit measures in tooltips is helpful. Noting that implicit aggregations tend to work more reliably in these cases will be valuable for others experiencing similar rendering and performance issues.
Pre-aggregating data in Power Query and connecting table fields directly to the visual is a practical way to enhance stability when working with high-volume geographic data.
Appreciate if you could share the feedback on our Microsoft Fabric Ideas. Which would be open for the user community to upvote & comment on. This allows our product teams to effectively prioritize your request against our existing feature backlog and gives insight into the potential impact of implementing the suggested feature.
Fabric Ideas - Microsoft Fabric Community
Thank you.