Forum Discussion

Anonymous's avatar
Anonymous
Not applicable
5 years ago

Visual error after measure is moved to another table in data model

Hi,

 

I have this test PBIX file with a simple measure. After I published it and created a report directly on Service and another one in Power BI Desktop using the dataset, if I change the measure from one table to another, both reports will show an error. It looks like the visual is still looking for the measure in the old table. This error will occur no matter how I move the measure or from which table to another.

 

I first noticed this issue in my production file and then replicated it in the the test file. Is this a known issue? Or is there something obvious I have missed. I searched on Google and here but didn't find an answer. 

Visual ErrorData Model

 

Patrick

3 Replies

  • aj1973's avatar
    aj1973
    Icon for Community Champion rankCommunity Champion

    Hi Anonymous 

    The measure is not related to a specific Table in the Model, they can be placed anywhere.

    I tried the exercice in my end, all works fine

     

    It could be a bug related to the page, delete the page and build a new one from scratch

     

    • Anonymous's avatar
      Anonymous
      Not applicable

      Thank you, Amine, for replying.

       

      The error does not occur in Power BI Desktp running the sample file. If I move the measure in the sample file and publish it again, reports built on Service or through live connection to the dataset will show the error.

       

      To replicate the error, could you try the following steps? 

      1. Publish the sample file to one of your workspaces.

      2. Build a report on Power BI Service using the measure in sample file dataset

      3. Move the measure to another table in Desktop running the sample file

      4. Publish the sample file again

      5. Open the report you just created on Service.

    • Anonymous's avatar
      Anonymous
      Not applicable

      Hi Amine,

       

      I tested on another computer with a June 2020 version and the got the same error. But this issue does not seem to affect Analyze in Excel.