Forum Discussion

atgeraci's avatar
atgeraci
Frequent Visitor
6 years ago
Solved

Custom Visual, Chiclet Slicer, Hierarchy Slicer error - Failure to render/load

Hello! I am getting an error when trying to add a Hierarchy Slicer to any reports I have previously made in PBI desktop.                  On a fresh PBI desktop file no such error occ...
  • atgeraci's avatar
    atgeraci
    6 years ago

    Tahreem24 Thanks for linking me to the similar problem! I posted my solution there, but will also post it here so that hopefully anyone with this probelm will find this!

     

    I realized that this issue has also impacted my other custom visual that I use - the Chiclet Slicer. So this is more of a custom visual interaction with PBI problem as opposed to a specific custom visual that hasn't been created properly.

     

    I tried following the advice found here but I am currently unable to find the cache location that was mentioned (I am very computer literate, I am thinking that doesn't exist for me. I did multiple searches using Search Everything to find the file after trying to navigate to the file manually)

     

    Then I hit upon this blog which details how to clear from within the PowerBI Desktop application. Once I cleared it I tried to use the slicer again. This failed as well.

     

    Then I found the folder I think you were referencing. The path was this: 

    <system drive>:\Users\<user>\Microsoft\Power BI Desktop Store App\CEF

    I deleted the cache folder and restarted PBI and... no dice.

     

    So then, I got a little bit clever (I think) and I deleted the Hierarchy Slicer custom visual from my report. Closed PBI and then deleted the aforementioned cache folder listed above. I re-opened the report and was met with success! I was able to add in new Hierarchy Slicers!

     

    I was still unable to add new Chiclet Slicers though, so I deleted that custom visual next. Closed PBI, and reopened the file and re-imported the visual from the marketplace and that worked too.

     

    TL;DR: I am not sure if the deletion of the cache folder is required but I know for sure that for me to make this work deleting the custom visual from the report and closing and reopening and re-importing the custom visual worked. (How to delete custom visuals below)