Forum Discussion

markuskolpext's avatar
markuskolpext
Frequent Visitor
3 months ago
Solved

Excel Pivot generates invalid MDX when collapsing nested hierarchies against Power BI dataset

When using a Power BI dataset in Excel, we get an error when using 2 nested dimensions and just try to collapse one of the elements. See error attached. We get this error with every dataset / semanti...
Need Help
  • collinq's avatar
    collinq
    3 months ago

    Hi markuskolpext ,

    This is a known bug and your workaround is still probably the best way and/or change your nesting (which is not even close to ideal).  Perhaps you can search for this issue in the Ideas and see if you can vote for it there.

collinq's avatar
collinq
Super User
3 months ago

Hi markuskolpext ,

This is a known bug and your workaround is still probably the best way and/or change your nesting (which is not even close to ideal).  Perhaps you can search for this issue in the Ideas and see if you can vote for it there.

AndreasPesak's avatar
AndreasPesak
Frequent Visitor
3 months ago

We also face it in our company now. Why is this topic solved?!?!

"This is a known bug". To whom? Microsoft? If it is a known bug, why can't I find it here: Microsoft Fabric Known Issues

What do you mean by vote an idea?! It's a new bug, shouldn't it be taken seriously by MSFT to bugfix it?

 

  • v-achippa's avatar
    v-achippa
    Community Support
    3 months ago

    Hi AndreasPesak,

     

    Thank you for reaching out to Microsoft Fabric Community.

     

    When we mention like known issue, it means it has already been identified and shared internally with Microsoft, even if it is not yet listed on the Microsoft Fabric Known Issues page.

    Since this looks like a separate case, could you please open a new thread with full details. So that we can look more into the issue and provide you the best solution possible.

     

    Thanks and regards,

    Anjan Kumar Chippa

    • AndreasPesak's avatar
      AndreasPesak
      Frequent Visitor
      3 months ago

      *<edit> Just tested it again, seems to work now as it should </edit>*

       

      Hi Anjan,

      what makes you think it is a separate case? It is the exactly the same one, the user must not collapse any separate row. Either all or nothing.

      Thanks for letting us know that Microsoft is aware of it.

       

      Best regards