Skip to main content

Configuration Reference

Environment Configuration​

Configure:

  • Workspace name
  • Lakehouse name
  • Source SQL Server connection values
  • SQL authentication method
  • Secret references
  • API endpoint and header requirements
  • Environment-specific table names

YAML Configuration​

Prepare or update:

  • build_request_db_config.yml
  • build_request_xml_config.yml
  • context_payload_config.yml
  • api_throughput_config.yml
  • filter_config.yml
  • filter_extensions_config.yml
  • process_pre_response_xml_config.yml
  • process_post_response_xml_config.yml
  • views_config.yml

The team must validate:

  • Root keys
  • Active and inactive mappings
  • Incremental columns
  • Repeated row identities
  • Static-value handling
  • Table names
  • Data types

Metadata Queries​

Validate or adjust:

  • Scenario metadata query
  • Source policy selection query
  • Any implementation-specific lookup or control-table reads

Target Model​

Define:

  • Target tables to be created
  • Target merge keys
  • Audit columns
  • Data retention or append strategy where applicable
  • Reporting view outputs if reporting is in scope

For the reporting mart, also define:

  • The SQL view inventory to be published from views_config.yml
  • Fact_PolicyPremium grain and key-resolution approach
  • Unknown-member behavior for dimension joins
  • Static versus configuration-driven dimensions

Reporting and Semantic Model​

When reporting is in scope, the implementation team must also configure:

  • Lakehouse SQL Analytics Endpoint connectivity for the semantic model
  • Semantic model table-to-view mappings
  • Report artifact names and workspace locations
  • DAX measure grouping and display-folder standards
  • Profile selector, currency, and display-format support tables where used
  • Application-to-report filter contract for embedded URL filters
  • Schema-drift automation notebook or equivalent operational process

Validate specifically:

  • ScenarioDB.ReportConfigurations entries used by Dim_Coverage and Rate_Report
  • Dynamic rate-component case expressions used by Rate_Report
  • Premium-band definitions used by Dim_PremiumChangeBand
  • Placeholder dimensions such as customer, agent, and agency when source integration is not yet available