Tabular Configuration

Tabular works with a couple of yamlA simple way to write configurations. It's basically a list that computers can read easily. files to generate the tabular model. To generate the correct model, it needs to understand the underlying datawarehouse/dataplatform. The underlying dataplatform has to supply the tables in a certain way (star-schema).

The following YAML files are available (* = mandatory):

• model.yaml*
• measure folder (multiple files with measures)
• measuretemplates.yaml
• roles.yaml
• formatstrings.yaml

The model configuration itself is not a standalone file: it is an entry in the models: list of the environment configuration (dp.<env>.yaml). A typical entry looks like this:

models:
- model: DM
  tabularName: DM
  compatibilityLevel: 1700
  addMembers: false
  DatabaseSchema: dbo
  workspace: FB-Demo-PRD
  DefaultPowerBIDataSourceVersion: powerBI_V3
  loginType: spn
  partitionDeployment: deploypartitions
  roleDeployment: RetainRoles
  lakehouse: Gold
  BimFolder: DM
  bimFile: Model.bim
  sourceQueryCulture: en-US
  ModelFolder: Models/DM
  ModelFile: model.yaml
  datasourceType: fabric
  datasourceName: DefaultDS
  LakehouseSourceConnection: Gold
  tabularSystemFolder: Technisch
  measureTemplateFile: measuretemplates.yaml
  formatStringFile: formatstrings.yaml
  roleFile: roles.yaml

See Configuration config for the full list of settings. A second entry in the same models: list can define a derived model by pointing DerivedModelFile at a derived YAML in the same ModelFolder.

note

The older DimkeyPrefix and DimPrefix settings are deprecated and will be removed in September 2026. Use DimSurrogatekeyPrefix and DimObjectPrefix instead.