Page Comparison

It is important to understand that filter logic is applied hierarchically, left to right - so in the example  "(1 OR 2) AND (3 OR 4)" The dataset returned will be filtered by (1 OR 2) before assessing "AND (3 OR 4)" condition - this means that any records removed by filters 1 or 2 are not available to meet the second part of the condition "AND (3 OR 4)"

It is also important to understand that when you update filter logic, it updates filter values but does not trigger the cascading filter check - cascading only kicks in on filter value selection or filter refresh.
Since the filter logic 'update' does not trigger the cascading filter check this could leave some filter values removed which do not need to be removed. For example, if we remove some criteria from a lower filter which would cause a prior filter to remove that value from the filter list, then when the lower filter value is removed while logic is changed it might prevent the upper filter from refreshing properly, etc.

A best practice is to add all required filters to a report before adding/changing the filter logic.