Skip to main content
The OBLIGOR_OVERRIDES table contains the override definitions for the Obligor table.

Unique Key

Override base table

The base table for these overrides is the Obligor table. To define Overrides you must add facts to the base table. For details on why this is required, see Overrides With DirectQuery.

Inject base table

For each override, you must generate multiple entries in the Obligor table with the following structure. Where:
  • Override Parameter: The parameters to determine where to apply this override.
  • Obligor Table Field: The field in the Obligor base table for this override.

Create base store tuples

See the Create Override Tuples section for an example of how to create the override tuples for the following override fields. These are the fields to override in the base override table, in this case the Obligor Table. These fields form an intermediate table containing the Override’s base store fields and will be merged back into the Override base table: Obligor.

Map override fields to base table fields

Once you create your tuples for each override field, you can then map the tuples back to the base store using the following relationship: