Forum Discussion

PaiYa's avatar
PaiYa
Frequent Visitor
1 year ago
Solved

Different Filed Name Between Power BI and Power Query

In the Power BI model, the field names are not fully aligned with those in Power Query (PQ). My data source is Dynamics 365 (Dataverse), and the specific connection code in Power Query is: = CommonD...
Need Help
PaiYa's avatar
PaiYa
Frequent Visitor
1 year ago

Hi jaineshp , thanks for your reply. Best Regards.

  • Solution 1: In fact, I have "Change Type" step before. And I try again in the test File(I remain only one column and remove all transform step except Data Load and Rename.). Still no,
  • Solution 2: It seems that you could not combine Remove Column and Rename Column in one step as this way.

     

  • Solution 3:
  • Solution 4: I found it! Clear Cache and refresh the data. Still no.
  • Solution 5: still no.
  • Solution 6: That's what I did. But as I said in the original post, " is inconvenient and may cause problems when making further updates.".

 

jaineshp's avatar
jaineshp
Memorable Member
1 year ago

Hey PaiYa,

Solution 1: Connection String Parameter Method

Try modifying your connection with additional parameters:

= CommonDataService.Database("***.crm.dynamics.com", [
CreateNavigationProperties=false,
UseDisplayNames=false,
Timeout=#duration(0,0,10,0) // Add timeout parameter
])

Solution 2: Complete Connection Recreation

  1. Delete the existing data source connection entirely (not just refresh)
  2. Close Power BI Desktop completely
  3. Clear Windows Credential Manager:
    • Windows Key + R → control keymgr.dll
    • Remove any Dynamics/CRM related credentials
  4. Reopen Power BI and create a fresh connection
  5. Apply renames immediately after connection (before any other transformations)

Solution 3: Alternative Data Source Method

Since this is a known Dataverse connector issue, consider using:

  • OData feed instead of Dataverse connector
  • Dynamics 365 (online) connector (if available)
  • Web API direct connection

Your OData URL would be: https://[yourorg].crm.dynamics.com/api/data/v9.2/

 

Solution 4: PowerShell Cache Clear

Sometimes Power BI's cache is deeper than the UI option:

  1. Close Power BI completely
  2. Navigate to: %localappdata%\Microsoft\Power BI Desktop\
  3. Delete the entire AnalysisServicesWorkspaces folder
  4. Restart Power BI

Solution 5: Registry-Level Fix (Advanced)

If you're comfortable with registry edits:

  1. Close Power BI
  2. Navigate to: HKEY_CURRENT_USER\Software\Microsoft\Microsoft Power BI Desktop\
  3. Look for cache-related keys and delete them
  4. Restart Power BI

Solution 6: Dataverse View Method

Create a custom view in Dataverse with your desired column names, then connect to that view instead of the raw table. This bypasses the metadata caching issue entirely.

Solution 7: Power Query Parameter Approach

let
Source = CommonDataService.Database("***.crm.dynamics.com"),
Navigation = Source{[Schema="dbo",Item="account"]}[Data],
// Force column recognition with explicit reference
RenameStep = Table.RenameColumns(Navigation, {{"accountid", "Account ID"}}),
// Immediately reference the renamed column to force recognition
TestColumn = Table.AddColumn(RenameStep, "Test", each [Account ID]),
RemoveTest = Table.RemoveColumns(TestColumn, {"Test"})
in
RemoveTest


Given your thorough testing, I suspect this is a Dataverse connector bug that may require Solution 8 (complete connection recreation) or Solution 12 (using Dataverse views) to resolve properly.


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

Best regards,
Jainesh Poojara / Power BI Developer