Slicer not updating the values in report

[Rdarshana]

Hello,
I am having an issue with a slicer that is not updating values based on tenant. 
I am using a currency slicer prompt on the report. The currency code is what is being used to display as slicer values.

The currency code comes from a currency table that is housed in the database. This table contains the distinct currencies for which a tenant contains data for. 
So, for tenant A - it may contains USD, GBP/. Tenant B - it may only contain EUR. Tenant C - USD, SGD, YEN

When I log in as Tenant A, I run the report as USD. 
Next, when I log in as Tenant B, I see that USD is pre-selected in the slicer. When I change it to EUR, then the report is automatically updated to EUR, and then, the slicer only shows EUR as the values. It no longer shows USD. 

What  I am trying to accomplish is that the slicer should display the distinct values of the currency code for that given tenant, and this is not how Power BI slicer seems to be working at the moment. 

We are not using USD as a default code on the report. 

I tried creating a DAX measure such that to explicitly display the tenant currencies, and used this as a filter on the currency slicer. BUt same behvaiour was noticed.

Has Tenant Data =

VAR SelectedCurrency = SELECTEDVALUE('Billing Currency'[Currency Code])

VAR TenantCurrencies =

    DISTINCT('Cloud Software Spend'[Billing Currency Code])

RETURN

IF(

    SelectedCurrency IN TenantCurrencies,

    1,   // keep this currency

    0    // hide this currency

)

Any suggestions?

[Poojara_D12 · Accepted solution]

Hi @Rdarshana 

The behavior you are seeing is a common side effect of how Power BI slicers interact with row-level filters and security contexts. When you log in as Tenant A and select USD, the selection is stored in the report filter context; then, when you switch to Tenant B, Power BI still tries to honor the previous slicer selection (USD), even though USD is not a valid value for Tenant B. Only after the model actually filters data to EUR does the slicer reduce itself to EUR. In other words, the slicer isn’t dynamically re-evaluating its available values on tenant change — it’s holding onto the existing selection until the model forces it to refresh. This is expected behavior with RLS and slicers because slicers do not automatically reset when security context changes.

To fix this, you have a few workable approaches. First, the ideal solution is to bind your slicer to a dimension table that already respects RLS, meaning your currency dimension must be filtered by tenant at the model level (not only via measure logic). If the currency table is not tied to tenant filtering, slicers won’t naturally show tenant-valid values. Second, instead of having users manually change tenants in the same session, consider using parameterized reports or bookmarks per tenant, or force a page refresh after changing tenant context — this clears slicer memory. Third, add a dedicated relationship or RLS rule linking tenants to currencies so that the slicer is only fed values valid to that tenant. Your DAX measure approach won't help because slicers require data-model filtering, not post-selection validation. Ultimately, the correct fix is to ensure the currency table itself is filtered by tenant context through proper RLS or relationships, so that the slicer values recalculate correctly as soon as the user context changes.

[Rdarshana]

@v-ssriganesh , @AnkitaaMishra 
This has not been resolved, as there does not seem to be a resolution yet. PowerBI does not allow for updating the slicer values unless it is manually changed. 

[v-ssriganesh]

Hello @Rdarshana,

I hope everything is going well for you. Has the solution suggested by @Poojara_D12 resolved your issue, or are you still experiencing any problems? Sharing an update could be helpful for others who might be facing the same situation.
thanks, @Poojara_D12 for sharing valuable insights.

Thank you.

[v-ssriganesh]

Hi @Rdarshana,

Thank you for posting your query in the Microsoft Fabric Community Forum, and thanks to @AnkitaaMishra for sharing valuable insights.

Could you please confirm if your query has been resolved by the provided solutions? This would be helpful for other members who may encounter similar issues.

Thank you for being part of the Microsoft Fabric Community.

[AnkitaaMishra]

Hi @Rdarshana , 

I tried to replicate this issue & tried a few DAX combinations and also tested with bookmark and page navigation approaches, but it seems like this is a limitation in Power BI slicers. The previous selection remains active even when the value doesn’t exist for the new tenant, so you’ll need to manually deselect the old slicer value.

Hopefully, Microsoft addresses this in a future update.