Forum Discussion
Discrepancy between report and backend query - dimension table issue
Hi vegasde100 ,
Thank you for reaching out to Microsoft Fabric Community.
Thank you FBergamaschi for the prompt response.
What you are seeing usually comes from a relationship/key integrity issue between your transaction fact table and the customer dimension. The amounts are correct because the fact table is fine, but the names shuffle when Power BI can’t consistently resolve the right customer. This often happens if the customer dimension has duplicate or non-unique keys, or if the fact table has missing/invalid CustomerIDs. When you refresh the model, the relationships temporarily realign, which is why it looks correct right after refresh. To fix it, ensure your Customer dimension has a unique key, check that all fact records have valid CustomerIDs, and confirm the relationship is one-to-many (dimension = one, fact = many). Once cleaned, the customer names will remain consistent with the amounts.
Thank you.
Hi vegasde100 ,
Thank you for reaching out to Microsoft Fabric Community.
Thank you FBergamaschi for the prompt response.
What you are seeing usually comes from a relationship/key integrity issue between your transaction fact table and the customer dimension. The amounts are correct because the fact table is fine, but the names shuffle when Power BI can’t consistently resolve the right customer. This often happens if the customer dimension has duplicate or non-unique keys, or if the fact table has missing/invalid CustomerIDs. When you refresh the model, the relationships temporarily realign, which is why it looks correct right after refresh. To fix it, ensure your Customer dimension has a unique key, check that all fact records have valid CustomerIDs, and confirm the relationship is one-to-many (dimension = one, fact = many). Once cleaned, the customer names will remain consistent with the amounts.
Thank you.
Thank you I'll look into this! This makes sense.