Hi @fraitas ,
You're encountering a common limitation in Power BI when working with Azure Maps and drillthrough functionality—specifically, the restriction that only a single value can be passed through drillthrough at a time. Unfortunately, Azure Maps does not support multi-selection drillthrough, and field parameters further complicate things by breaking drillthrough altogether.
A practical workaround, though not a perfect replica of Qlik View's behavior, would be to avoid drillthrough altogether and instead consolidate your experience into a single scrollable page. In this approach, you place the Azure Map at the top, allowing users to select multiple regions (e.g., cities), and below that, use synchronized visuals like tables and charts that respond to those selections dynamically.
While this method can feel a bit crowded, using containers and grouping can help keep it organized and visually balanced. You could also implement a toggle (e.g., via bookmarks or field parameters) to switch between map layers (City, County, etc.), though care must be taken to ensure the underlying selections persist between views. Another option would be to use a slicer (e.g., for geography level) alongside a standard map visual, which supports better filtering flexibility than Azure Maps.
While this solution lacks some of the interactivity of a true drillthrough, it enables multi-selection and real-time filtering without breaking context. Ultimately, combining a thoughtfully structured scrollable report with synced visuals may offer the most seamless and performant user experience within Power BI’s current limitations.
Passionate about leveraging data analytics to drive strategic decision-making and foster business growth.
Connect with me on LinkedIn: Rohit Kumar.
