Power BI：‘Merge Queries as new’内连接无法匹配行及切片器失效求助

Let’s break down the likely culprits here and how to fix them—since you know this worked in a copy, it’s almost certainly a subtle data or setting difference that’s throwing things off.

1. Data Type Mismatch on CompanyLocationGUID #

This is the #1 reason merges fail even when matching records exist.

• Head to the Power Query Editor, pull up both Dim_Companies and Fact_Premium tables.
• Check the data type of CompanyLocationGUID in each table. If one is set to Text and the other to GUID (or even Whole Number vs Text), Power Query won’t recognize the matches.
• Fix it: Right-click the column > Change Type > align both tables to the same type (usually Text is safest for GUIDs to avoid formatting quirks).

2. Hidden Spaces or Invisible Characters #

Even if the GUIDs look identical, extra leading/trailing spaces or non-printable characters can break matching.

• In Power Query, add a custom column to both tables with this formula:

  Text.Trim([CompanyLocationGUID])
  

• Try merging using this trimmed column instead. If it works, replace the original column with the cleaned-up version permanently.

3. Broken or Inactive Relationships #

If the merge issue is resolved but the slicer still doesn’t work, your model relationships might be misconfigured:

• Switch to Model View in Power BI Desktop. Verify there’s an active relationship between Dim_Companies[CompanyLocationGUID] and Fact_Premium[CompanyLocationGUID].
• Ensure the relationship is set to Single (not Many-to-Many unless intentional) and cross-filter direction is set to Both (or at least from the dimension table to the fact table).
• If the relationship is grayed out (inactive), right-click it > Activate.

4. Duplicate or Null Records #

Duplicate GUIDs in Dim_Companies or null values in either table can confuse Power Query’s merge detection:

• In Power Query, select Dim_Companies > go to Home > Remove Rows > Remove Duplicates (choose CompanyLocationGUID as the key column).
• Filter out any null values in CompanyLocationGUID from both tables before attempting the merge.

5. Minor File Corruption or Cache Glitch #

Since this worked in a copy, your current PBIX might have a tiny corruption issue:

• Try copying the tables from your working report into the current one (use Power Query’s Copy Table function).
• Or, save the file, close Power BI, clear the cache (File > Options and settings > Options > Data Load > Clear Cache), then reopen and retry the merge.

Once you fix the merge issue, your slicer should behave exactly as it did in your working report—since the underlying connection between the company dimension and premium fact table will be properly established.

内容的提问来源于stack exchange，提问作者Serdia