"Invalid number" error using Interactive Report search on collection
734426Dec 30 2010 — edited Jan 13 2011hi -- I have several interactive reports based on collections. In the IR reqion query definition,
I cast the collection values as needed (number, date, etc). Everything's been working great.
In both development and production, I can use the search feature of interactive reports
and it finds rows containing the text I type in (as well as everything else working fine...)
I just imported a new version of an application into our production database. Now, when I use the
interactive report search, I always get "invalid number". This even happens on interactive reports
that still work in the previous version of the production application... and these IRS
have not been modified at all.
If I create a filter and search for "elevation" in a string column, the filter works. If I create a filter
searching for "elevation" in a number column, I get "invalid number". (In the development
environment, I can do the latter -- it just doesn't find any rows.)
Clearly it's choking on the types of the columns in the IR... but why now and not before, and why
in the production database but not the development DB? Both are running 4.0.1.00.03.
This is a pretty major loss of functionality... and it comes at a really bad time... Help?!
Thanks,
Carol