Forum Discussion

Caelan's avatar
Caelan
Frequent Visitor
2 years ago
Solved

Custom hierarchy giving error when published

Hi,

 

I've got a custom hierachy - basic one, 2 text fields only - on a column chart. Works fine in desktop, but when published to service I get this:

 

 

 

Can anyone suggest a fix please?

  • Caelan's avatar
    Caelan
    2 years ago

    Thank you for your help Adamk.

     

    I'm not sure whether this was the issue; I looked at the data in service and it was recognising these columns, and I was able to build tables with them and they were behaving correctly.

     

    Before deleting it, I re-published from desktop, and the visuals are working now, even when refreshed in service. Odd one - looks like it just didn't want to do any work on Friday. Don't blame it. Will give your solution a crack if the issue occurs again.

3 Replies

  • Anonymous's avatar
    Anonymous
    Not applicable

    Hi Caelan ,

     

    There was a change to the underlying dataset, which is causing problems. The error message refers to a column named Office HierarchyFE Name, which is not in your data model screenshot.

     

    You should go into powerbi.com and delete the dataset for this project and recreate/republish it.

     

    Best Regards,
    Adamk Kong

     

    If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

    • Caelan's avatar
      Caelan
      Frequent Visitor

      Thank you for your help Adamk.

       

      I'm not sure whether this was the issue; I looked at the data in service and it was recognising these columns, and I was able to build tables with them and they were behaving correctly.

       

      Before deleting it, I re-published from desktop, and the visuals are working now, even when refreshed in service. Odd one - looks like it just didn't want to do any work on Friday. Don't blame it. Will give your solution a crack if the issue occurs again.

      • Anonymous's avatar
        Anonymous
        Not applicable

        Hi Caelan ,

         

        Okay, looking forward to your feedback.

         

        Best Regards,
        Adamk Kong