Forum Discussion

Anonymous's avatar
Anonymous
Not applicable
4 years ago
Solved

Measure Name already exists while no double names

Hello,

 

I keep getting the following message when I refresh my Power BI dataset in the desktop version:

I get the message 'The name <MeasureName> is already used for a measure on table <TableName>. Choose a different name.'. The message is repeated for each table name, even though I do not see the connection between the measure and that specific table.

 

I received this message after executing the following steps:

  1. I downloaded the PBI file from PBI service.
  2. Clicked on refresh (a column that was just created in an Azure SQL DB table is added to the dataset).
  3. I open PowerQueryEditor
  4. Add a new table. The table should not be the problem, although it creates relationships with some other tables.
  5. Close & Apply in PQE. It closes and starts a small refresh, I get no errors.
  6. I click on the refresh button (so that it refreshes all tables), and I get the error of the screenshot above. 

Does somebody know what the problem can be? It is sensitive data so I am not able to share the PBI file here.

 

Thanks in advance!

  • Anonymous's avatar
    Anonymous
    4 years ago

    v-luwang-msft Thanks for your time testing it. I was able to solve the problem. In PowerQuery Editor, I changed the columns name from ColumnA to ColumnAHidden (so that it matches the renamed col name in the reporting view). This solved the problem.

     

    Still feels very strange that I only got the error when adding a non-related table. Seems like a bug.

7 Replies

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

    Anonymous Is there a measure with the same name as a column that has a home table of that column? Or is the new table name the same name as an existing measure?

    • Anonymous's avatar
      Anonymous
      Not applicable

      Greg_Deckler , thanks for your message. No the table name is not the name of a measure. I changed the name of the table already a few times in PowerQueryEditor and got no different result. When I look in the search field the measure name (that is shown in the error), I only find the measure in the table that is also shown in the error message.

      When I open PowerQueryEditor again, delete the newly added table and do a total refresh again, I do not get the error message anymore, so I am pretty confident it has to do something with the table.

      Is it possible that the table creates relationships with other tables that create this error?

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

        Anonymous No, the relationships shouldn't matter. You can turn off the auto-recognition of relationships though and try it. Maybe you used a reserve word for the table? Hard to say. You could check the Issues forum here:

        https://community.powerbi.com/t5/Issues/idb-p/Issues

        And if it is not there, then you could post it.

        If you have Pro account you could try to open a support ticket. If you have a Pro account it is free. Go to https://support.powerbi.com. Scroll down and click "CREATE SUPPORT TICKET".

  • v-luwang-msft's avatar
    v-luwang-msft
    Icon for Community Support rankCommunity Support

    Hi Anonymous ,

    I tried to restore your scenario, but no such problem occurred.

    base table:

    Close and apply:

     

    create measure:

    visual:

    And has your problem been solved, if so, please  share your own solution to help others find it.

    Best Regards
    Lucien

     

     

     

    • Anonymous's avatar
      Anonymous
      Not applicable

      v-luwang-msft Thanks for your time testing it. I was able to solve the problem. In PowerQuery Editor, I changed the columns name from ColumnA to ColumnAHidden (so that it matches the renamed col name in the reporting view). This solved the problem.

       

      Still feels very strange that I only got the error when adding a non-related table. Seems like a bug.