Version Valid From Term (Dataflow Model Object)
Applies to
Platform: Microsoft SQL Server · Snowflake · Snowflake dbt · Databricks · Databricks dbt · Fabric Lakehouse · Fabric Warehouse · Oracle
Architecture: Data Store · Data Vault · Data Mart
Version Valid From Term (ValidFromSourceTerm) names the source term that holds the start of validity of each source version. Set it when a source delivers several versions of a key, so that the loader stores them as separate versions with their own BG_ValidFromTimestamp. Up to Generator 2.0 the property was named ValidFrom Source Term.
Supported objects
- Store Entity, Satellite, Link Satellite, Business Satellite and Business Link Satellite: the property switches on a multi-version load.
- Mart Dimension: the property names the validity term of a historized source.
Set the value
- Open Manage Term Mappings of the target model object.
- Open the menu of the source model object and choose Edit Dataflow Model Object.
- In the Historization group, select the source term in Version Valid From Term, for example
UPDATE_DATE, and save. The default is empty.
The property belongs to one source model object of one dataflow set. A model object with a multi-version load has one dataflow, one dataflow set and no aggregation.
Effect on generated output
- The source view adds the column
BG_ValidFromTimestamp_<alias>, where<alias>is the alias of the source model object, for examples1. A NULL source value becomes Begin of Universe. - Each source version becomes a version with this value as
BG_ValidFromTimestamp. - Satellites load only versions that start later than the newest stored version of the key. Earlier versions and versions with the same start are skipped without a warning. Available since Generator 2.4.
- On a Store Entity, a mapping of
BG_ValidFromTimestamphas no effect, and validation reports warning ID-10058.
Example
A Satellite on Microsoft SQL Server uses UPDATE_DATE as Version Valid From Term. The first load delivers employee 1 with the addresses Street A from 2026-01-01 and Street B from 2026-03-01, and employee 2 with Street X and a NULL date. The second load delivers employee 1 with Street C from 2026-02-01, Street D from 2026-03-01 and Street E from 2026-04-01. The result view then shows:
ADDRESS_LINE1 BG_ValidFromTimestamp BG_ValidToTimestamp Street X 1900-01-01 00:00 +00:00 9999-12-31 00:00 +00:00 Street A 2026-01-01 00:00 +00:00 2026-03-01 00:00 +00:00 Street B 2026-03-01 00:00 +00:00 2026-04-01 00:00 +00:00 Street E 2026-04-01 00:00 +00:00 9999-12-31 00:00 +00:00
The first row is employee 2; the other rows are employee 1. The second load added only the version from 2026-04-01.
Related articles
- Previous: Edit a Dataflow Model Object
- Reference: BG_ValidFromTimestamp, Begin of Universe (Project)
- See also: Configure a multi-version load, Dataflows amount with multi-version load (Business Rule), Dataflow Sets amount with multi-version load (Business Rule), Aggregation with multi-version load (Business Rule)