Hi @louzensf
Based on the details you provided, it sounds like a tweak to searching by product name caused unexpected behavior during data loading. While circular references can certainly cause such problems, the problem could also lie elsewhere, as you mentioned that any circular references in the relationship are not recognized.
Please try the following ways to resolve the issue:
Go back to the modified query and make sure the logic is correct. Sometimes, inadvertently including or not being specific enough filters can result in a data set that is much larger than expected.
Verify that the relationships between tables are set up correctly. Incorrect relationships (for example, a many-to-many relationship where one-to-many is expected) may cause more rows to be loaded.
Review each step applied to the query in Power Query and make sure no steps inadvertently duplicate rows or otherwise extend the data set.
Consider whether the data model can be optimized to prevent performance issues. This may include summarizing data, creating indexes, or pre-aggregating values.
Make sure any report-level filters or slicers are applied correctly and don't inadvertently cause problems.
This can also be a factor if the data source has limitations in how it handles queries, especially when searching by product name. Make sure the data source is optimized for the type of query you are running.
Use the Performance Analyzer in Power BI Desktop to see which parts of the report are taking the longest to load. This helps pinpoint where the problem may be occurring.
You can view the link below for more details:
Understand star schema and the importance for Power BI - Power BI | Microsoft Learn
Use Performance Analyzer to examine report element performance in Power BI Desktop - Power BI | Micr...
Regards,
Nono Chen
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
