Valid from timestamp mapped without effect (Business Rule)

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

These business rules warn when BG_ValidFromTimestamp is mapped on a Store Entity or an Entity where the mapping has no effect. Both rules raise a warning, and generation continues: ID-10057 when the model object is not historized, and ID-10058 when it uses a multi-version load.

Messages

Each message names the model object and its type in place of <model object name> and <type>. The Generate Artifacts page lists the messages without the rule ID.

Model object is not historized

The client shows a warning with this text:

Model object '<model object name>' of type '<type>' has valid from
timestamp (BG_ValidFromTimestamp) mapped but is not historized.
Without historization the mapping will have no effect.

On the model object card, point to the warning icon to see this message with the rule ID: Warning ID-10057.

Cause: BG_ValidFromTimestamp has an expression or a default value in a dataflow set, while no relationship and no term has Historization Type SCD2. Business keys, identities and Default Terms are not counted. The rule checks Store Entity and Entity.
Fix: clear the mapping of BG_ValidFromTimestamp, or set Historization Type SCD2 on the terms or relationships that keep history.

Model object uses a multi-version load

The client shows a warning with this text:

Model object '<model object name>' of type '<type>' has valid from
timestamp (BG_ValidFromTimestamp) mapped and has Multi Version Load
configured. With active Multi Version Load the mapping will have no
effect, and instead the configured version valid from timestamp will
be used.

On the model object card, point to the warning icon to see this message with the rule ID: Warning ID-10058.

Cause: BG_ValidFromTimestamp is mapped, and a source model object of a dataflow set has a Version Valid From Term, which switches on the multi-version load. The rule checks Store Entity.
Fix: clear the mapping of BG_ValidFromTimestamp. The load takes the valid-from value from the Version Valid From Term.

Available since Generator 2.2.

Check the result

The warning icon is gone from the model object.

Example

In a Dimensional project on Microsoft SQL Server, the Entity common_customer_scd1 has only SCD1 terms. Its BG_ValidFromTimestamp is mapped to CAST('2020-01-01' AS DATETIME2). The client shows:

Model object 'common_customer_scd1' of type 'Entity' has valid from
timestamp (BG_ValidFromTimestamp) mapped but is not historized.
Without historization the mapping will have no effect.