Have you managed to identify what had caused the error? I mean I've started just recently see this error, but the report was created a month ago, as well as the slicer was added, and I really didn't change anything in Power BI config since the beginnig of July. So my point is, how reliable will be the new update of the slicer? In case there is a chance that any new update of Power BI will resuscitate the bug, hmm,let's say it will make our reports rather unstable.
Thanks for quick feedback! Not sure if I fully understand though since I recently started to use PBI.
I'll put it like this: how do make the unexpected error message to disappear (without changing slicer type obviously)? Should I wait for a new release of PBI desktop? Download the hierarchy slicer again? Do nothing and wait for the hierarchy slicer to "update itself"? Something else?