When using SQL data fetchers with incoming status rules, I noticed that TBSM tries to embed threshold filters inside SQL logic. It is successfull when SQL is very simple. But when the custom SQL contains grouping function or subquery, the TBSM places its conditions in wrong place of the query.
Because of this, those rules aren't working.
I can't create any views in production system just for simplifying queries.
Is there a method for disabling TBSM to break custom queries?