"The name 'x' is already used for a column on table 'y'. Choose a different name"

[ngd_99]

Since I got February 2024 update for Power Bi Desktop (v2.126.927.0), I keep getting this message with ALL calculated columns in ALL tables, where it says the column x is already used in table y. I have checked and can confirm that calculated column with name x ONLY exists one time (not duplicated) ONLY in table y (so it makes no sense to point that out as an issue by Power BI). It happens with all calculated columns in all my files, which before the update did not cause any problem.

Any idea hoy to solve this issue or what may be causing it?

 

[jcp_ti_user10]

I have the some error after created more than one calculated column on the same table witch has data from another table as a result of a LOOKUPVALUE function. 
Is this your case?
If I delete these columns the error disappear. This behavier only exists on recent updates.

[abhishekrws01]

Hi - Yes, i have the same issue. Even if you remove the column, it continues until you delete all the calculated column. Some time the table name becomes the column name too.

[abhishekrws01]

I am having the same issue after Feb-2024 version. Seems like this is an issue

[bklosowski]

Same bug here. I think it's related to one of the PReview features, I guess Visual Calculations. 

I've switched most Preview Features off and apparently the bug doesn't occur anymore. 

EDIT: I was wrong. The bug keeps happening even after deactivating the preview functions. 

[Crabbendam]

Interesting, did not seem to work for me though.

[bklosowski]

Nevermind, I was wrong. 

I thought it was related to the preview functions but it's not. It kept happening even after I had most of them deactivated. 

I'll edit my previous reply. 

[Jaime_Castillo]

Same problem here! 100% sure there aren't duplicated names, but the message still appears for calculated columns. I'm with February 2024 version.

[KaanY]

We're also getting this since this February 2024 update. It is highly infuriating and distracting, and so difficult to ignore.
Have tried simplyfying column names, but nothing seems to get rid of the error.

[ngd_99]

I have found no solution so far that works for February 2024 update. However, I downgraded to previously available release (November 2023 when I did - now you have December 2023 available) and the error stopped appearing. You can find these versions here:

Previous monthly updates to Power BI Desktop and the Power BI service - Power BI | Microsoft Learn

I know it is not an optimal solution but it worked for me. I will remain in this previous version until this gets fixed or someone knows exactly why it may be happening.

[alex20274]

Agree with above, Im now just ignoring.

[alex20274]

Im having the exact same problem, clearing cache has not resovled the issue, as a test I have opened prior reports and the issue now appears with any calculated column which didnt at the time when created. Therefore assume its to do with the lastest update. 

[v-yilong-msft]

Hi @ngd_99 ,

Based on your problems, here are my answers.

Please check for hidden columns, sometimes hidden columns or columns in other tables can cause conflicts, make sure there are no hidden columns with the same name in other tables. To check for hidden columns, go to the “Model” view in Power BI Desktop and expand all tables to verify if any other columns share the same name.

Clear the Power BI Desktop cache by going to “File” > “Options and settings” > “Options” > “Data Load” > “Clear Cache.” Restart Power BI Desktop to see if the issue persists.

Best Regards

Yilong Zhou

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

[KaanY]

Clearing the cache doesn't help.
I've seen other odd things like to unhide a page you have to click "Hide" again.
When I see little things like this is feels like a release that wasn't fully tested.

[CadenKream]

Sorry - clearing cache does not help.

I am able to make changes to the calcualted column (which save and reflect in Report View), but after after moving to another column, the pop-up appears.

It can be ignored but it's quite annoying.