Skip to content
Contact us Go to Customer Portal
  • There are no suggestions because the search field is empty.

Current View and History View sources (Business Rule)

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

These business rules check the source model objects in a dataflow set of a Current View or History View, including the Business variants. A dataflow set may have at most one PIT, needs exactly one satellite when it has no PIT, and may have no PIT when it maps the hash key of a Driving Key Link. Each rule raises an error, which blocks generation in the client: ID-20002, ID-20003 and ID-20005.

Messages

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

More than one PIT

The client shows an error with this text. For a Business Current View or Business History View, the details name Business PIT.

Model object '<model object name>' of type '<type>' can have 0 or 1
source model objects of type PIT .

On the model object card, point to the error icon to see this message with the rule ID: Error ID-20002.

Cause: a dataflow set of the view has two or more PIT sources.
Fix: keep one PIT in the dataflow set and remove the others.

No PIT and not exactly one satellite

The client shows an error with this text:

Model object '<model object name>' of type '<type>' can have exactly
1 Source Model Object of type Satellite when no Model Object of type
of type PIT  is used.

On the model object card, point to the error icon to see this message with the rule ID: Error ID-20003.

Cause: a dataflow set without a PIT has no satellite source or more than one. Satellites here are Satellite, Link Satellite and their Effectivity and Business variants.
Fix: keep exactly one satellite in the dataflow set, or read the satellites through a PIT.

Driving Key Link with a PIT

The client shows an error with this text:

Model object '<model object name>' of type '<type>' can not have
source model objects of type PIT , if a Driving Key Hash Key is used.
Please contact our support.

On the model object card, point to the error icon to see this message with the rule ID: Error ID-20005.

Cause: a dataflow set has a Driving Key Link or Business Driving Key Link as source, maps its DrivingKeyLink_HK, and also has a PIT source.
Fix: remove the PIT from the dataflow set and read one satellite, or remove the mapping of DrivingKeyLink_HK. The message asks you to contact biGENIUS support for this combination.

The Driving Key Link rule is available since Generator 2.0.

Check the result

The error icon is gone from the view, and generation is no longer blocked by it.

Example

In a Data Vault project on Microsoft SQL Server, the Current View based_on_hub_with_pit_rcv gets the PIT load_based_on_lnk as a second PIT source. The client shows:

Model object 'based_on_hub_with_pit_rcv' of type 'Current View' can
have 0 or 1 source model objects of type PIT .

Related articles