Just highlighting what we see as a major problem with the filtering logic in custom reports. Consider the following filters:
or
You would expect these filters to return the same data. In fact, the first filter will return no data.
The reason is that if using MSSQL DB, the code does not handle the 'Equals' operator correctly resulting in a SQL query that returns no data.
Again, this really should be caught during testing phases and appears to be in the product for some time resulting in hundreds of our custom reports being invalid.