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 update. That’s an insightful observation about the differences in behavior between explicit measures and implicit aggregations in Azure Maps.
Your findings will be helpful for others dealing with large datasets and similar rendering issues. Hopefully, Microsoft will enhance the visual’s performance and optimization in future updates.
Thank you.
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.