Implementation Type Incremental Filter (Business Rule)
Applies to
Platform: Microsoft SQL Server · Snowflake · Databricks · Fabric Lakehouse · Fabric Warehouse · Oracle
Architecture: Stage
This business rule checks that a Stage with Implementation Type Virtual has no incremental load. It raises an error, which blocks generation in the client until you fix it. The rule ID is ID-10020.
Message
The client shows an error with this text on the Stage. <model object name> and <type> stand for its name and type.
Model object '<model object name>' of type '<type>' has implementation type 'Virtual' and incremental load defined. This is only supported with implementation type 'Permanent', 'FactLoadStrategy' or 'Cached'.
On the model object card, point to the error icon to see this message with the rule ID: Error ID-10020. The Generate Artifacts page lists the message without the ID.

Cause
Implementation Type of the Stage is Virtual, and the Default Term BG_IncrementalFilter has a term mapping with an expression or a default value.
Fix
Do one of the following:
- Set Implementation Type of the Stage to
Cachedin Edit Model Object. A Stage supportsCachedandVirtual, see Implementation Type (Model Object). - Clear the term mapping of
BG_IncrementalFilterin Manage Term Mappings, if the Stage needs no incremental load.
Check the result
The error icon is gone from the Stage, and generation is no longer blocked by it.
Example
In a Stage project on Microsoft SQL Server, the Stage load_incremental has BG_IncrementalFilter mapped and gets Implementation Type Virtual. The client shows:
Model object 'load_incremental' of type 'Stage' has implementation type 'Virtual' and incremental load defined. This is only supported with implementation type 'Permanent', 'FactLoadStrategy' or 'Cached'.
Related articles
- Reference: Implementation Type (Model Object), BG_IncrementalFilter
- See also: Configure an incremental load, Stage, Understand warnings and errors