Skip to content

EntiHub Documentation

BI / Semantic Reference Layer

BI / Semantic Reference Layer

Reference dimensions (channel, country groupings, product hierarchies for BI) live as approved entities with consumption views in the warehouse.

Why this is needed

Conflicting dashboards start with conflicting dimensions.
Stewards need a UI; BI needs SQL views.
Classic reference-data MDM still belongs in EntiHub.

Proposed entities in EntiHub

Governance settings

Setting	Recommended value	Why
`approvalRequired`	`true`	Dimension changes affect all reports.
`historyEnabled`	`true`	Restate historical groupings when needed.
`allowSameAuthorApproval`	`false`	Maker/checker separation for sensitive changes.
`deletedRetentionDays`	`90` (or higher)	Soft-delete retention for auditability.

Entity definition (YAML sketch)

name: bi_channel
displayName: BI channel
domain: BI
description: BI channel
version: "1.0.0"
approvalRequired: true
historyEnabled: true
deletedRetentionDays: 90
displayRefColumn: channel_code
uniqueConstraints:
  - name: uq_bi_channel_channel_code
    columns: [channel_code]
consumption:
  views:
    - schema: mdm_consume
      name: vw_bi_channel
      apiName: bi-channel
columns:
  - name: channel_code
    dataType: string
    nullable: false
    maxLength: 32
  - name: channel_name
    dataType: string
    nullable: false
    maxLength: 128
  - name: channel_group
    dataType: string
    nullable: false
    maxLength: 64
  - name: status
    dataType: string
    nullable: false
    maxLength: 16

YAML sketches

Sketches highlight the important fields and governance flags. Trim or extend columns to match your domain. See Setup Entity for the full YAML reference.

Sample data

channel_code	channel_name	channel_group	status
WEB	Web direct	Digital	active
PARTNER	Partner resale	Indirect	active
FIELD	Field sales	Direct	active

Benefits for the company

One Channel/Country definition across reports.
Warehouse-native consumption for Fabric.
Steward-friendly maintenance.