Effectivity end mapped while calculated (Business Rule)

This business rule warns when an effectivity satellite calculates BG_Effectivity_End from BG_Effectivity_Begin and BG_Effectivity_End is also mapped. The result view then shows the calculated end instead of the mapped one. The rule raises warning ID-20004, and generation continues.

Message

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

Model object '<model object name>' of type '<type>' has property
'CalculateEffectivityEndFromEffectivityBegin' enabled and term
'BG_Effectivity_End' mapped. Effectivity end will be overwritten in
result view.

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

Cause

Calculate Effectivity End From Begin is true on the satellite, which the message names CalculateEffectivityEndFromEffectivityBegin. At the same time BG_Effectivity_End has an expression or a default value in a dataflow set.

Fix

Choose the end you want:

• Calculated end: clear the mapping of BG_Effectivity_End in Manage Term Mappings.
• Mapped end: set Calculate Effectivity End From Begin to false in Edit Model Object.

Check the result

The warning icon is gone from the satellite.

Example

In a Data Vault project on Microsoft SQL Server, the Effectivity Link Satellite load_loyaltycard_elsat has Calculate Effectivity End From Begin true and maps BG_Effectivity_End. The client shows:

Model object 'load_loyaltycard_elsat' of type 'Effectivity Link
Satellite' has property 'CalculateEffectivityEndFromEffectivityBegin'
enabled and term 'BG_Effectivity_End' mapped. Effectivity end will be
overwritten in result view.

Related articles

• Reference: Calculate Effectivity End From Begin (Model Object), BG_Effectivity_End, BG_Effectivity_Begin
• See also: Effectivity Satellite, Effectivity Link Satellite, Understand warnings and errors