Skip to main content
Microsoft Idea

    Power BI

    New

    Make getSlicerState() work for slicers with multiple fields and/or hierarchy fields

    Vote (29) Share
    Lode Cools's profile image

    Lode Cools on 12 Mar 2021 11:28:01

    The API method getSlicerState() (https://docs.microsoft.com/en-us/javascript/api/overview/powerbi/control-report-slicers) currently does not work when the slicer contains multiple fields or when the slicer is a hierarchical slicer (multiple fields combined into one).

    This is very limiting for a rich embedding experience and basically voids the complete use case of 'getting' & 'setting' slicers.

    The only workaround is too create non-power-bi slicers in the embedding application, and set hidden 'one-field' slicers in the embedded report.

    Comments (4)
    Lode Cools's profile image Profile Picture

    Andreu fil on 19 Apr 2024 17:50:15

    RE: Make getSlicerState() work for slicers with multiple fields and/or hierarchy fields

    Good information, thankssehackear.top

    Lode Cools's profile image Profile Picture

    Aaron Johnson on 19 Apr 2022 20:11:01

    RE: Make getSlicerState() work for slicers with multiple fields and/or hierarchy fields

    We strongly agree with both the comments - this should be treated as a BUG not a nice-to-have.

    Lode Cools's profile image Profile Picture

    Colin McCaleb on 08 Apr 2022 14:09:22

    RE: Make getSlicerState() work for slicers with multiple fields and/or hierarchy fields

    This is a common use case and is preventing us from embedding and working with our Power BI reports in a SPA application. Any updates on when this will be fixed?

    Lode Cools's profile image Profile Picture

    Kari Sinivuori on 20 Nov 2021 11:40:56

    RE: Make getSlicerState() work for slicers with multiple fields and/or hierarchy fields

    This API error prevents us to use hierarcy slicers in embeded reports. Hierarcy slicers are comon use case and separating hierarcy into individual slicers is no a viable solution any more. This bug has been around long enough - just fix it! This error needs to fixed asap.