Dashboard marcadores não respeitam os filtros de datas

[Paulosaraiva]

EN - I'm having a problem with a dashboard. To give you some context, I created the dashboard with dates in a range of days, and the panel is saved in markers (indicators). The data option is unchecked because the goal is for the filter to stay within the last 2 years (current date - 24 months) for each new day. However, I've tried several ways and the platform doesn't update from one day to the next (the maximum date remains the last saved date).

PT-BR - Estou com um problema em um dashboard , para contextualizar eu criar o dashboard com a data entre dias , e o painel esta salvo em marcadores (indicadores)  , a opção de dados esta desmarcado pois o objetivo é que a cada novo dia o filtro fique entre os ultimos 2 anos (data atual - 24 meses) . contudo já tentendi de varias formas e a plataforma não atualiza de um dia para o outro (data maxima continua a ultima data salva).

Alguém já passou por isso e conseguiu de alguma forma resolver ? 

[v-echaithra]

Hi @Paulosaraiva ,

We wanted to kindly follow up regarding your query. If you need any further assistance, please reach out.
Thank you.

[v-echaithra]

Hi @Paulosaraiva ,

We’d like to follow up regarding the recent concern. Kindly confirm whether the issue has been resolved, or if further assistance is still required. We are available to support you and are committed to helping you reach a resolution.

Thank you.

[arabalca · Accepted solution]

Hi @Paulosaraiva ,

What you are describing is a known behavior in Power BI. Date range slicers typically work best when they start in a cleared state when creating bookmarks. Special care is needed when configuring bookmarks with this type of slicer, as they can capture static values. Learn:  https://learn.microsoft.com/en-us/power-bi/visuals/power-bi-visualization-troubleshoot

The most reliable solution for your case I think that is to use a native Power BI relative date filter. Instead of selecting a fixed date range, configure the slicer in relative date mode and select "last 24 months". This type of filter recalculates automatically every day and is fully compatible with bookmarks.

If you prefer not to rely on the visual state of the bookmark, another option is to move that filter to the page or report level, where the behavior is more predictable.

On another note, if you ever consider an alternative within the Microsoft Fabric ecosystem, there is a feature called Fabric Maps, integrated into Real-Time Intelligence, that allows you to visualize static or real-time spatial data directly from a Lakehouse or Eventhouse, without depending on Power BI bookmarks. There is also ArcGIS Maps integration if you work with more advanced geospatial data: https://learn.microsoft.com/es-es/fabric/real-time-intelligence/map/create-map

If this response has been helpful, please don't forget to give it a Like and mark it as a Solution so other community members can find it easily.

Thank you!

[radwanalmsora]

Hello, I completely understand your frustration as Azure Maps evaluates the spatial location pipeline independently from standard visual filters to build its tile layers. When a measure like Average Stat is added to the tooltips, it forces a context transition for every row being evaluated across your two million records, which causes your validation check to see active filters where it shouldn't and crashes the canvas.

​The most efficient solution is to intercept the data stream before it hits the map by embedding the filter logic directly inside a secure location measure instead of dragging the raw column into the visual location slot. You can achieve this by creating a new measure named Secure ZIP Location using a conditional statement that checks if the ZIP or County or State fields are filtered. If any of those slicers are active, the measure returns the selected value of the ZIP code, and if not, it returns a blank status.

​Once you create this measure, clear out the raw ZIP column from your Azure Map's Location well completely and replace it by dragging this new Secure ZIP Location measure straight into that slot. Because the map now sees an empty dataset when no slicers are set, it completely bypasses the tooltip evaluation loop for your two million rows, stopping the crash instantly while rendering perfectly the moment a user interacts with your State, County, or ZIP slicers.