Different Filed Name Between Power BI and Power Query

Hi v-hjannapu 

I try almost each way offered, but none of them worked. I think it may be a "bug" of application. Anyway,

thank them for their kindly help and your attention.

Hey PaiYa,

Looking at your screenshots and the issue you're describing, this appears to be a known behavior with Dataverse/Dynamics 365 connections in Power BI. Let me provide you with some targeted solutions:

Root Cause

This is a known issue with Dataverse connections where Power BI's metadata cache doesn't always reflect Power Query column renames, especially for system fields like accountid, name, etc.

Solution 1: Force Metadata Refresh (Recommended)

// In Power Query, after your rename step, add this:
= Table.TransformColumnTypes(#"Renamed Columns", {{"Account ID", type text}, {"Account Name", type text}})


This forces Power BI to recognize the new column names by explicitly setting data types.


Solution 2: Alternative Rename Method


Instead of Table.RenameColumns, try using Table.SelectColumns with new names:


= Table.SelectColumns(#"Previous Step", {
{"accountid", "Account ID"},
{"name", "Account Name"},
// Add other columns you need
})

Solution 3: Dataverse-Specific Workaround

= CommonDataService.Database("***.crm.dynamics.com", [
CreateNavigationProperties=false,
UseDisplayNames=false // Add this parameter
])

Solution 4: Clear Power BI Cache (Correct Location)

The cache clearing option is actually here:

• File > Options and Settings > Options
• Data Load tab (left panel)
• Data Cache Management Options
• Click Clear Cache

Solution 5: Column Recreation Method

What I meant by "remove and add back":

1. In Power Query, use Table.RemoveColumns to remove the problematic column
2. Then use Table.AddColumn to create a new column with the desired name, copying data from another source column
3. This forces a complete metadata refresh
   
   // Example:
   #"Removed Column" = Table.RemoveColumns(#"Previous Step", {"accountid"}),
   #"Added Custom" = Table.AddColumn(#"Removed Column", "Account ID", each [accountid_backup])
   
   

Solution 6: Model-Level Fix

If Power Query renames still don't work:

1. In the Model view, select the problematic columns
2. In the Properties pane, change the Display Name
3. This overrides the Power Query name for report purposes

Prevention Tips

• Always apply column renames as the last transformation step
• Avoid renaming Dataverse system columns if possible
• Use Display Names in the model instead for user-facing names
• Consider using calculated columns with DAX if renames persist in failing

Did it work? ✔ Give a Kudo • Mark as Solution – help others too!

Best regards,
Jainesh Poojara / Power BI Developer

Hi PaiYa ,

When I refer Desktop is the Power BI Desktop. What I mean is after you have done the load from the Power Query just double click the column name or Right click and select rename the column. Has I refer this will generate a step on Power Query automatically.

Then refresh the model and check if the name persists or not.