Forum Discussion
Ghost Rows in Power BI Report from Direct Lake Semantic Model
hi, jbauer22
Double-check the data in the source (Lakehouse) to make sure there are no spurious records in it. Use a SQL query to confirm that the records you see in Power BI do not exist in the source.
Verify that the filters you apply to your measures are working properly and not causing unexpected results. If possible, consider simplifying relationships. Although you mentioned that you want to understand the defects rather than use a solution, simplifying the model may help isolate the problem.
Use the simplified model to create a separate Power BI report to test if the issue persists with minimal data and relationships.
hackcrr
If this post helps, then please consider Accept it as the solution and kudos to this post to help the other members find it more quickly
Thanks for the response. We just triple checked the records in the lakehouse and confirmed those records do not exist when we query the fact_ledger table directly. The semantic model screen shot in the original post is the simplified version to recreate the issue. The many to many relationship seems to be causing time travel on the fact_ledger delta table. We believe this to be a defect.