This project is read-only.

Column 'actualValue' does not allow nulls

Sep 20, 2010 at 10:47 AM

Hello Oraylis !

   Thank you for the rand new Release 2.0.0.

I have a question concerning a point that is not related specifically to the new release.

For some queries there might be NUll values. However this does not seem to be allowed for the actual result table.

System.Data.NoNullAllowedException : Column 'actualValue' does not allow nulls."

Is there a possibility to switch this constraint off ?

Thank you in advance.


Oct 11, 2010 at 4:14 PM

Hi folks,

same question here. this makes testing of large datasets quite impossible since it mostly has some null-values.  i don't remember such behavior at prior version anyway, so can this constraint be switched off?

best regards, Martin

Oct 12, 2010 at 2:54 PM


we are working on a new release of BI.Quality, which solves the null-value issue. The new version is expected to be online next week.

Best regards,

Oct 25, 2010 at 9:04 AM


we are happy to announce that the new version of BI.Quality has just been released. The null value problem discribed in this threat has been fixed in the new release.

Best regards,