Dynamic hierarchy using fields parameter works on desktop but not on cloud service

[kshe]

Hi,

We are using the dynamic hierarchy built from field parameter to select different level for Matrix and drill down.

It's working perfectly before but suddenly not working on service today. Any idea? It's still working perfectly on desktop.

On service, when I click and unclick 'Level 2', it won't go back to default 'Level 1', it stays on 'Level 2'.

Also when I select both 'Level 2' and 'Level 3', I cannot drill down to 'Level 3' on the matrix. It shows 'Level 2' only.

Any change from Power BI service side today?

Thanks.
K

[JTBrownPGIM]

We too are noticing an issue on our side exactly the same.  Users are not happy.  Behavior seems to have changed within the past week or so, in the Power BI service (Fabric) itself.

Steps to reproduce:
1. Create a field parameter

2. Assign hierarchy related fields from one dim in order.

3. Assign hierarchy related fields from another dim with fewer fields in order.

4. Create a calculated column to group the fields into groups relative to their hierarchy.

5. Place the field parameter on the ROWS well of a matrix, and place some measure on the matrix to roll up.

6. Create a hierarchy slicer based on the field parameter with the group column first, then the field parameter column as second.  Make the slicer multi-select.

7.  Select the first grouping with more columns.  The matrix rolls up to the top level.

8. De-select the first grouping with more columns and select the second grouping with fewer columns.  The matrix rolls up to the top level.

9. De-select the second grouping and select the first, the matrix correctly rolls back up to the top level.

10. Publish the report to Fabric workspace and repeat steps 7-9.  In the Fabric service online, the drill-level for the matrix will not correctly re-set when transitioning back from group2 to group1 - it always shows the lowest level of whatever was selected with Group 2.

Really annoying.

[lbendlin]

There's a long explanation in the Power BI blog for the July 2025 version. Not that it makes it any better but at least they explain why they did it.

Power BI July 2025 Feature Summary | Microsoft Power BI Blog | Microsoft Power BI

[V-yubandi-msft]

Hi @kshe  ,
Is everything clear now, or do you need any more information or clarification.

Thank you.

[V-yubandi-msft]

Hi @kshe ,

Could you please update us on the status of your issue? Has it been resolved, or have you reached out to Microsoft support for help? Let us know if you still need any assistance.

[V-yubandi-msft]

Hello @kshe ,

May I check if you've raised a support ticket for this issue, or is it working fine on your end now? Based on community responses, it seems to be working intermittently some users are experiencing issues while others are not. Just wanted to confirm your current status so we can assist further if needed.

Thanks&regards,

Yugandhar.

[V-yubandi-msft]

Hi @kshe ,

Thank you for engaging with the Microsoft Fabric Community. I tested the report with a dynamic hierarchy using field parameters and found that the issue only occurs in Power BI Service. In Power BI Desktop, everything works as expected slicer selections and drill downs reset properly to Level 1 when higher levels are unchecked.

In the Service, after selecting Level 2, unchecking it does not bring back Level 1, and the drill down feature gets stuck, not allowing navigation past intermediate levels. This appears to be a recent change in how the Matrix visual manages field parameter context online.

FYI:

I haven’t seen any official updates from Microsoft, but the problem is consistent across workspaces. Thanks to @rohit1991 , for helping confirm this. For now, we recommend users work in Desktop for full hierarchy and drill features until this is resolved in the Service.

Regards,

Yugandhar.

[lbendlin]

Can you pinpoint when it stopped working?

[Dominoes2]

Just wondering, that page with all of the Powerbi Service versions looks like it is in the powerbi service? How does one find that page? 

[lbendlin]

That page is a SharePoint list we maintain internally with Power Automate to keep track, precisely because Microsoft are very secretive about service version changes.

[V-yubandi-msft]

Hi @Dominoes2 ,

To find your current Power BI Service version, open Power BI in your browser, click the question mark icon at the top right, and choose About Power BI  from the dropdown. A pop up will show information like the Service version, Client version, data location, and last update time.

This feature gives you the latest build details, but Microsoft does not provide a complete public version history. Detailed version logs with release dates are usually from internal dashboards, which are not available to the public.

If you want to make it even more polished for a community post or documentation, you could add a quick note about alternative resources like:

Previous monthly updates to Power BI Desktop and the Power BI service - Power BI | Microsoft Learn
Use semantic model version history (preview) - Power BI | Microsoft Learn

Hope this helps...

[kshe]

working all the way till 7/11/25 PST.

[lbendlin]

They pushed a new service version yesterday - can you try again?

[slilley]

Not working for me either.  We have dynamic field parameters in matrices throughout embedded applications and they are not working consistently.

Would appreciate any workarounds anyone has.

[Dominoes2]

I have tried just now and the issue still persists. Do you know of any work arounds for the interim or when mirosoft is going to have a fix out? 

[lbendlin]

If you have a Pro license you can open a Pro ticket at https://admin.powerplatform.microsoft.com/newsupportticket/powerbi
Otherwise you can raise an issue at https://community.fabric.microsoft.com/t5/Issues/idb-p/Issues .

[kshe]

Thanks. I noticed today the drill down is working. However the default view back to the highest Level is still not working as before.

[V-yubandi-msft]

Hi @kshe , @Dominoes2  & @slilley ,

Can you raise a support ticket with Microsoft for further investigation. MS team will be able to look into the issue more thoroughly and help resolve it.

How to create a Fabric and Power BI Support ticket - Power BI | Microsoft Learn

Thanks &regards,

Yugandhar.

[slilley]

Working better for me this morning - maybe they rolled back - anyone else?
<crossing fingers>

[Rom_Cheng]

Seems to work on my side too,  it doesn't work a few hours ago but works now.

[Dominoes2]

I have talked to microsoft support who did confirm that a fix for this issue was released. I have gone through and tested some of the reports I have and found that it was resolved. However in some cases, depending what state the user left the report in, they would need unselect and reslect the chosen row parameters.