CRM Power BI

[Satuk]

Hi, I faced today a strange problem with my desktop datamodel that is connected to crm dynamics 365. I made few changes in power query to the script of one query. In power query everything looks ok but when I apply & close, in Desktop field names of that particular query orgin from CRM. I.e. I lost my name conversion (local language) and table column names are in english. This has not happened before. Table column are the same plus two extras that I added to the script. Any idea why desktop overlooks naming convention of power query?

[Ritaf1983 · Accepted solution]

Hi @Satuk 

The issue you're describing—where column names in Power BI Desktop revert to the original CRM Dynamics 365 field names after changes in Power Query—is a known issue that can occur in certain scenarios. The possible reasons include:

1. **Metadata Re-syncing**: Power BI automatically synchronizes column names from the data source (in this case, CRM) when the data model is refreshed. If you modified the Power Query script or added new columns, Power BI might have re-synced the metadata from CRM, causing the column names to revert to their original, English field names.

2. **Change in Field Mapping**: If your local naming conventions were applied in Power Query or manually adjusted in the model view, changes to the underlying query might reset these mappings. Power BI could be applying the default schema from Dynamics 365 again.

3. **Schema Changes in CRM**: If there were recent updates or changes in the CRM Dynamics 365 system, such as modifications to entity fields or the schema, this could affect how Power BI retrieves metadata during the data load.

### Possible Solutions:

- **Reapply Custom Names**: After closing Power Query, manually reapply your local language naming conventions in the model view in Power BI Desktop. This manual renaming should persist unless there is a metadata refresh issue.

- **Disable Auto-Detect in Power Query**: Ensure that Power Query is not set to auto-detect data types and metadata, as this could override your custom column names. You can check this under the "Options" menu in Power BI Desktop under Power Query settings.

- **Re-check Changes in Dynamics 365**: Verify that no recent schema or field changes were made in Dynamics 365 that could affect the column names, particularly if you added or modified fields recently.

- **Consider Using Dataflows**: If you encounter this issue frequently, consider moving your transformations into Power BI Dataflows, where you can maintain the custom column names independently of the desktop model refresh.

### If Nothing Helps:
If none of these solutions work, you can open a support ticket with Microsoft for Power BI, especially when it involves integration with Dynamics 365. Here is the link to submit a support ticket:

[Power BI Support - Open a ticket](https://powerbi.microsoft.com/support/)

You'll need to sign in with your work or school account and select the relevant options regarding your issue. Be sure to include as much detail as possible, such as screenshots, error messages, and steps to reproduce the problem.

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