Synchronisation: semantic changes on `ignore nulls` with `synchronize` statement

[forums]

The synchronize statement enables users to replicate and/or synchronise data between multiple platforms, data sets or tables. For more information see:

Synchronise your Data with one Statement across multiple Applications

Go to Dutch version Summary A global innovation on top of Invantive SQL enables one-statement synchronization (mono- as well as bi-directional) of reference data between applications. This note is the first of a series and explains the advantages, the concept and the grammar. Data Synchronization for Reduced Costs and Happy Customers With the advent of apps, your business data has gotten distributed across multiple apps instead of all in one big ERP-system. Apps make your business agile and re…

Starting release 25.0.127, the semantics of ignore nulls have changed since the implementation had two variants, each one occurring in different cases. The now logic is:

• ignore nulls on identified by: ignore changes with null values during identification of rows (vertical filtering).
• ignore nulls on values: ignore changes with null values on all columns.
• ignore nulls on all: ignore changes with null values on all columns and during identification of rows.

When ignore nulls is used without postfix, the meaning is ignore nulls on all, which is different from the previous most frequent occurring default now represented by ignore nulls on identified by. In case the new default does not work correct, please make sure to use instead ignore nulls on identified by.