Why should you avoid bidirectional cross-filtering?

Setting cross-filter direction to Both makes filters flow in both directions, which in a model with several fact tables creates ambiguous filter paths the engine may resolve unexpectedly. It can also cause circular dependency errors.

When one measure genuinely needs the effect, use CROSSFILTER inside CALCULATE — local and explicit, rather than a global model change.

Legitimate exceptions exist, notably some row-level security propagation, but they should be deliberate rather than default.