Some logical constructions can cause issues for WhereClause of report view can cause issues, for example if OR is used without parenthesis - it is better to surround the where clause with parenthesis always
Environment
None
Activity
Show:
Carlos Ruiz April 27, 2015 at 2:06 PM
Thanks , you're 100% right.
BTW, this is the test case to check the previous bug:
in seed database
as System
Change whereclause of report view RV_Allocation to "Amount=50 OR (DiscountAmt= 0 OR C_CashLine_ID>=0)"
as GardenAdmin
Execute report "Allocation", fill the parameter BP with Standard -> bug, records from BP<>Standard are shown
Armen Rizal April 27, 2015 at 9:09 AM
Is it better to put the paranthesis after the line if (!Util.isEmpty(whereClause)) { ?
Major
Some logical constructions can cause issues for WhereClause of report view can cause issues, for example if OR is used without parenthesis - it is better to surround the where clause with parenthesis always