Building integrations

Why does a Yes/No filter or update on a dataset give wrong results?

A Yes/No column can also be empty, so filter with Not equal to Yes instead of Equal to No.

Fix

Short answer: Filter with Not equal to Yes instead of Equal to No. To write a Yes/No value from a process, set it with a condition in an integration.

Why it happens

Internally, a Yes/No column has three states: true, false and empty (null). A filter for "No" matches only false, so it skips rows where the value is empty.

How to fix it

To filter correctly:

  1. In your filter, pick the Yes/No field.
  2. Choose the Not equal to operator.
  3. Set the value to Yes.

To write a Yes/No value into a dataset from a process:

  1. Create an integration that updates the dataset.
  2. Add a condition or conditional paths based on the source value.
  3. In each path, set the Yes/No field to the matching value.

Note

Kissflow plans to change Yes/No fields to use only two states in a future release.

Related answers