Forum Discussion
Discrepancy between report and backend query - dimension table issue
- 1 year ago
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.
I am not sure I understood.
Are youreferring to Power BI Service only or are you comparing Service with Desktop?
The Desktop and the Service will show the same results at the refresh time, different results before or after (unless you manually refresh the Desktop anytime you automatically refresh the Service)
Please clarify this as first thing
Thanks
If this helped, please consider giving kudos and mark as a solution
me in replies or I'll lose your thread
Want to check your DAX skills? Answer my biweekly DAX challenges on the kubisco Linkedin page
Consider voting this Power BI idea
Francesco Bergamaschi
MBA, M.Eng, M.Econ, Professor of BI
Thanks for the response. Sorry I should have better clarified. I'm ultimately comparing across the service version but at different poitns in time as v-venuppu pointed out. I believe I understand his explanation for it!