With Orion 9.1 SP5:
When creating a custom report, particularly using custom pollers, I've run across two major bugs:
1: Sorting a numeric value works in the Orion NPM console, but on the web interface, the field is always treated as a string. Even when prefixing the values (IE: FormatData 000, to make all numbers 3 digits) or explicitely setting the data type to NumericData, this occurs. This results in a value of 2 being greater than a value of 19. I've also reproduced this bug with Node Availability.
Does anyone have a workaround for this bug?
2: Custom poller values don't seem to be correctly cast in a custom report, causing a SQL error to be thrown when you try to limit to TOP XX or TOP %. I have found a workaround for this:
In my case, when looking at the actual query in the custom report (Using wordpad), the datatype was being cast as "Real" rather than "integer". I changed this manually to integer and the problem was resolved; Orion's report editor did not break the report from that point forward.
