2016-02-04 13:02:00
Topic starter
While debugging a report, I see that certain ModelLink filter fields that are left blank return with a negative values such as -128 or -1226216161. Why does that happen?
This usually happens if the 'Filters' tags in the report file are defined as
<Filters bindSqlNulls="false>.
Yeah, this is a legacy flag which should always be true for any new report you create. For some reason someone thought it was a good idea a long time ago to use these "magic" numbers instead of real nulls, so this is part of our legacy codebase. bindSqlNulls="true" is STRONGLY preferred.