Power BI DirectQuery: Child table shows exceeds 100,000 row error after adding applying a measure

Hi Zhinee , Thank you for reaching out to the Microsoft Community Forum.

It looks like the key issue is that your Session filter isn't propagating its filtering effect to the Joblet table, even though you'd expect a parent-child relationship to do this. This often happens in DirectQuery mode if there's a disconnect in the relationship setup or because your filters and visual-level logic (such as with custom measures) don't trigger the automatic propagation. If the Joblet table isn't properly linked or the relationship isn't enforced (for example, with referential integrity or correct cross-filter direction), the child table visual can end up displaying all records or run into row-limit errors when a measure filter is applied.

Double-check your relationship settings. Enabling Assume Referential Integrity (if your data meets the requirement that all child keys exist in the parent) may help Power BI use more efficient queries and more predictable filter propagation. Also, confirm your storage modes, tables set to DirectQuery or Dual can behave differently, especially when complex filters and slicers are involved. If rows are still not correctly limited, review your relationship direction (single vs. bidirectional) in the model so that the Session table's selection flows down to Joblet and restricts data as expected.

Model relationships in Power BI Desktop - Power BI | Microsoft Learn

Assume Referential Integrity setting in Power BI Desktop - Power BI | Microsoft Learn

Table Storage Mode in Power BI Semantic Models - Power BI | Microsoft Learn

Add a filter to a report in Power BI - Power BI | Microsoft Learn

Bidirectional cross-filtering in Power BI Desktop - Power BI | Microsoft Learn

Filter context in DAX - SQLBI