It is just an example of creating a custom query report that uses OR in the WHERE clause. The current 2.5 (and apparently 2.6) version of ER does not support an automatic OR clause. That is why a custom query report may have come in handy to overcome…