HubDB "Is Null" filter not working (__is_null) but Not Null is

[mgoswick]

I've run into an issue with the HubDB API and usage in the Design Manager where some tables will not properly filter with the "Is Null" filter. It is the same issue as was outlined here (https://community.hubspot.com/t5/APIs-Integrations/Null-Filter-is-Not-working-in-Hubdb-is-null/m-p/2...)

Table where filter doesn't work

https://api.hubapi.com/hubdb/api/v2/tables/669114/rows?portalId=2035844&VOD__is_null=&orderBy=-date&limit=1&offset=0

Table where filter does work

https://api.hubapi.com/hubdb/api/v2/tables/667804/rows?portalId=2035844&VOD__is_null=&orderBy=-date&limit=1&offset=0

It should be noted that the filter "Not Null" (__not_null=) works on both tables, so I know it's not an issue with an internal name typo or something else.

Example on table where is null doesn't work

https://api.hubapi.com/hubdb/api/v2/tables/669114/rows?portalId=2035844&VOD__not_null=&orderBy=-date&limit=1&offset=0

Reference :https://developers.hubspot.com/docs/methods/hubdb/get_table_rows

Any help would be appreciated. 

[cbarley]

Hi @mgoswick , I'm working with Jason, the support rep you chatted with, on this one. This certainly seems unexpected. Reaching out to our product team as we speak to get eyes on this.

[mgoswick · Accepted solution]

Working with the support rep, the issue was resolved. Just setting the column to either =0 (fales) or =1 (true) works. 

So in the example above, the parameter should be VOD=0 or VOD=1 instead of using the __is_null or __not_null filters.