I don’t see anything wrong with your syntax, but not having visibility to your data values it’s hard to determine further what might be going wrong. For instance, you have with your match() function to test if [car code] begins with a “V” (denoted by “V*”), but what if there is a leading space in the data, or something else that you are not expecting?
Your final example where you want to get a subset of cars with condition rate >0, is probably not going to work the way you’re thinking unless you add a second grid to your report. The reason is that as the report processes, it can only deal with a row (or aggregation) once, hence once a record passes through as true (a hit) then work is done and output is displayed. The report processor cannot regurgitate the record again to do something else for you (at least not with the basic functionality offered in WebI). You would have to set up “hold” registers, comparators, and more breaks, all of which I don’t think you’ll be able to do in WebI. An alternative that I’ve done from time to time is to put another block side-by-side to the first block to “simulate” this second sub-handling. Good luck with your report.
thank you John, As of now that is how im displaying my data. But i wanted to see if any of the BO gurus have any work around for this issue. Anyway that advice helped me a lot. thanks once again