The quick answer
Enable Use Expressions and group each OR branch with parentheses. Keep filters that must constrain every branch outside the combined OR group, joined with AND. Preview the rows after each change to test the logic.
The screenshots use sample data and fictional person and operating-company names.
Before you start
This example edits an existing unsummarized transaction search, Regional Order Review. It uses item-line amounts and keeps Main Line, Tax Line, Shipping Line, and COGS Line false. Amount means the signed line amount, not the transaction total. Check the sign behavior for your transaction types. You need access to view and edit this existing search.
01. Review the starting filters
Open Reports → Saved Searches → Regional Order Review. On Criteria → Standard, review the four line-scope filters, the Sales Order/Invoice/Cash Sale types, July–August 2026 dates, and Amount greater than $2,500. Preview the baseline: both the date and amount conditions must hold.
02. Group the two qualifying branches
Return to Criteria and enable Use Expressions. Build (Type AND Date) OR (Amount AND Type), using the same allowed types in both branches. Put an outer pair of parentheses around those branches and keep all four line-scope filters outside, connected with AND.
03. Compare the broader results
Click Preview. With the example data, the search now includes the recent $640.00 Cobalt Adapter line and the older $6,275.00 Summit Storage line. Either the date branch or the amount branch can qualify a row. Compare document numbers, dates, items, and amounts with the baseline.
04. Exclude the item across both branches
Return to Criteria and add Item for Aster Rack Server. Select Not on that condition. Close the outer OR group before joining the exclusion with AND, so it applies whichever branch qualified the line.
05. Check the final preview
Preview again. The Aster Rack Server lines are absent, while Beacon Hub, Cobalt Adapter, and Summit Storage remain. SO9027 still appears through its Beacon Hub line: this excludes item lines, not whole transactions. This demonstration ends at Preview; save the definition separately when you intend to retain it.
Check the result
- Both OR branches retain the allowed transaction types.
- All common line filters and the item exclusion constrain the combined group.
- The example’s final preview has three rows; the search was not saved.
Common questions
How do AND, OR, and parentheses affect a saved search?
AND requires every condition; OR allows either branch to qualify. Parentheses control grouping. Keep shared line filters (Main Line, Tax Line, Shipping Line, and COGS Line set to false) outside the grouped OR expression so every branch remains constrained.
How can I include recent sales or high-value sales?
Use two grouped branches joined with OR: one requiring the allowed transaction Type and recent Date, and another requiring the allowed Type and line Amount above the threshold. Repeat the type restriction in both branches to prevent unintended transaction types.
How do I exclude an item from both OR branches?
Add the item condition as Item is not the excluded item, then join it with AND outside the outer parentheses containing both OR branches. This makes the exclusion apply regardless of which branch qualified.
Why does a transaction still appear after excluding one item?
This search returns item lines, not necessarily unique transactions. Excluding an item removes its qualifying line, but another qualifying line from the same transaction can remain. To validate the logic, preview before and after, inspect document numbers and items, and remember previewing does not save changes.