PowerBI setSlicerState fails to set Hierarchy Slicer when executed through Python (JavaScript API)

[MicrosoftUser42]

I have a JSON with multiple reports configurations, each item has a slicers key, which again contains multiple slicer definitions that look like this:

"slicers": [
    {
        "slicer_filter": {
            "$schema": "http://powerbi.com/product/schema#hierarchy",
            "target": [
                {
                    "table": "Regional Hierarchy",
                    "column": "Lead Country"
                },
                {
                    "table": "Regional Hierarchy",
                    "column": "Country"
                }
            ],
            "filterType": 9,
            "hierarchyData": [
                {
                    "operator": "Selected",
                    "value": "LC Austria"
                }
            ]
        },
        "slicer_id": "e076ac766bb91090aa01"
    },
    ...
]

This hierarchy filter specifically causes issues. The slicer filter works perfectly fine, when I use it in the Playground like this:

const filter = {
            "$schema": "http://powerbi.com/product/schema#hierarchy",
            "target": [
                {
                    "table": "Regional Hierarchy",
                    "column": "Lead Country"
                },
                {
                    "table": "Regional Hierarchy",
                    "column": "Country"
                }
            ],
            "filterType": 9,
            "hierarchyData": [
                {
                    "operator": "Selected",
                    "value": "LC Austria"
                }
            ]
        };

// Retrieve the page collection and get the visuals for the active page.
try {
    const pages = await report.getPages();

    // Retrieve the active page.
    let page = pages.filter(function (page) {
        return page.isActive;
    })[0];

    const visuals = await page.getVisuals();

    // Retrieve the target visual.
    let slicer = visuals.filter(function (visual) {
        return visual.type === "slicer" && visual.name === "e076ac766bb91090aa01";
    })[0];

    // Set the slicer state which contains the slicer filters.
    await slicer.setSlicerState({ filters: [filter] });
    console.log("Slicer was set.");
}
catch (errors) {
    console.log(errors);
}

But when I use the exact same filter using python like this:

for slicer in slicers:
  slicer_id = slicer["slicer_id"]
  slicer_filter = slicer["slicer_filter"]
  result = driver.execute_async_script(f"""
      var callback = arguments[0];
      (async function() {{
          const filter = {slicer_filter};
          try {{
              const pages = await report.getPages();
              let page = pages.filter(function(page) {{
                  return page.isActive;
              }})[0];

              const visuals = await page.getVisuals();
              let slicer = visuals.filter(function(visual) {{
                  return visual.type === "slicer" && visual.name === "{slicer_id}";
              }})[0];

              await slicer.setSlicerState({{ filters: [filter] }});
              
              callback("Slicer was set.");
          }} catch (errors) {{
              callback("Error: " + JSON.stringify(errors, null, 2));
          }}
      }})();
    """)
  print(result)

I get:

Error: {
  "message": "slicerTargetDoesNotMatch",
  "detailedMessage": "Filters target doesn't match slicer target",
  "level": 3
}

The approach I am using does work for basic slicers like:

{
    "slicer_filter": {
        "$schema": "http://powerbi.com/product/schema#basic",
        "target": {
            "table": "Fiscal Calendar",
            "column": "Fiscal Year"
        },
        "operator": "In",
        "values": [2025],
        "filterType": 1
    },
    "slicer_id": "d1e2c93c8009480134b1"
}

For those, I get:

Slicer was set.

Am I missing something?

Best Regards

[MicrosoftUser42 · Accepted solution]

Excuse me I was not using the latest version of powerbi-client. Since hierarchy slicers have only been added in a later release, the target of the slicer was reported incorrectly to the API.
Using the latest stable version of powerbi-client fixed the issue:
<script src="https://cdn.jsdelivr.net/npm/powerbi-client@2.23.1/dist/powerbi.min.js"></script>