No delete detection with an incremental load in the source (Business Rule)

Applies to
Platform: Microsoft SQL Server · Snowflake · Databricks · Fabric Lakehouse · Fabric Warehouse · Oracle
Architecture: Data Store

This business rule warns when a Store Entity uses delete detection without a Delete Detection Source while a source model object is loaded incrementally. It raises a warning, and generation continues. The rule ID is ID-10045.

Message

The client shows a warning with this text on the model object. <model object name> and <type> stand for its name and type.

Model object '<model object name>' of type '<type>' has source objects,
which are loaded incrementally and has no delete detection source
configured. This might lead to unexpected results.

On the model object card, point to the warning icon to see this message with the rule ID: Warning ID-10045. The Generate Artifacts page lists the message without the ID.

Cause

Delete Detection Method of the Store Entity is not None, Delete Detection Source is empty, and a source model object of its dataflows maps the Default Term BG_IncrementalFilter, which makes it an incremental load. The rule checks only the source model objects that the Store Entity reads directly.

Fix

Do one of the following in Edit Model Object of the Store Entity:

Select a model object that delivers the business keys for delete detection in Delete Detection Source. With FullSet, it must deliver the full set of valid business keys.
Set Delete Detection Method to None.

Check the result

The warning icon is gone from the Store Entity.

Example

In a Data Store project on Microsoft SQL Server, the Store Entity load_incremental_source gets Delete Detection Method FullSet without a Delete Detection Source. Its source model object salestransaction_inc is loaded incrementally. The client shows:

Model object 'load_incremental_source' of type 'Store Entity' has source
objects, which are loaded incrementally and has no delete detection
source configured. This might lead to unexpected results.