Column exchange with a calculated column?

[TA_]

Hello,

I am stuck with the following problem; I need to edit a column cointaining unique keys. Unfortunately, a number of keys have changed within the last year or so. There is an operation to compare changes of objectives attached to those keys. Therefore, changes of unique keys lead to an exclusion of those objectives from the comparison, since the check-up will not be able to recognize, that two different keys are in fact one single objective.

I have already created a new calculated column with the correct keys. Unfortunately i can not delete the old column and rename the new one, since I used a lookupvalue function directed to the old column.

My Idea was, that i could name swap the columns in the Power Query. What i did not know at the time is, that a calculated column wont show up in the power query. 

I hope there is a clever solution to my problem, except of renaming the used "key Column" in every single calculation of the dashboard.

[TA_]

Hey Felix,

thank you for your fast response 😀.

To give you more context, I am comparing different buildings with each other. These are seperated in WE, but each WE has different ME in it. And to create a unique key for each specific part of a building, there is a key column ID_WE_ME that cointains the correct combination of the specific unit in Format like this: 12345/01.

Since a few Objectives changed their WE/ME, I uploaded a table cointaining a mapping for these changes (MAP_WE_ME), where you can read for example that 12345/01 is from the start of 2025 56789/01. Then I calculated a new column (ID_ME_WE#) within my original table (Info) containing the needed information about the units, aswell as the key ID_WE_ME. My dax code looks like this: 

ID_WE_ME# = 

COALESCE(

    LOOKUPVALUE(

        Map_WE_ME[NewKey],

        Map_WE_ME[OldKey], Info[ID_WE_ME]

    ),

    Info[ID_WE_ME]

)

To specific the procedure, I compare the same units from year 2024 to 2025.

I do not know if it is possible to recreate the ID_WE_ME# within the powerquery, if possible it would kinda solve all my issues.

[MFelix]

Hi @TA_ ,

I don't know how you are calculating the new column but I would redo that column in Power Query that way you can then rename or delete the previous column if not necessary.

Another question is that if you are doing a Lookupvalue function to generate a new column in another table I would also pass this calcution to the Power Query using the Merge option between queries this would allow more flexibility and ensure consistancy.

Can you please give more context on what you are calculating and how?