Power BI Semantic Modelling
Guide users in building optimised, well-documented Power BI semantic models following Microsoft best practices.
When to Use This Skill
Use this skill when users ask about:
- Creating or optimising Power BI semantic models
- Designing star schemas (dimension/fact tables)
- Writing DAX measures or calculated columns
- Configuring table relationships (cardinality, cross-filter)
- Implementing row-level security (RLS)
- Naming conventions for tables, columns, measures
- Adding descriptions and documentation to models
- Performance tuning and optimisation
- Calculation groups and field parameters
- Model validation and best practice checks
Trigger phrases: "create a measure", "add relationship", "star schema", "optimise model", "DAX formula", "RLS", "naming convention", "model documentation", "cardinality", "cross-filter"
Prerequisites
Required Tools
- Power BI Modelling MCP Server: Required for connecting to and modifying semantic models
- Enables: connection_operations, table_operations, measure_operations, relationship_operations, etc.
- Must be configured and running to interact with models
Optional Dependencies
- Microsoft Learn MCP Server: Recommended for researching latest best practices
- Enables: microsoft_docs_search, microsoft_docs_fetch
- Use for complex scenarios, new features, and official documentation
Workflow
1. Connect and Analyse First
Before providing any modelling guidance, always examine the current model state:
1. List connections: connection_operations(operation: "ListConnections")
2. If no connection, check for local instances: connection_operations(operation: "ListLocalInstances")
3. Connect to the model (Desktop or Fabric)
4. Get model overview: model_operations(operation: "Get")
5. List tables: table_operations(operation: "List")
6. List relationships: relationship_operations(operation: "List")
7. List measures: measure_operations(operation: "List")
2. Evaluate Model Health
After connecting, assess the model against best practices:
- Star Schema: Are tables properly classified as dimension or fact?
- Relationships: Correct cardinality? Minimal bidirectional filters?
- Naming: Human-readable, consistent naming conventions?
- Documentation: Do tables, columns, measures have descriptions?
- Measures: Explicit measures for key calculations?
- Hidden Fields: Are technical columns hidden from report view?
3. Provide Targeted Guidance
Based on analysis, guide improvements using references:
- Star schema design: See star-schema.md
- Relationship configuration: See relationships.md
- DAX measures and naming: See measures-dax.md
- Performance optimisation: See performance.md
- Row-level security: See rls.md
Quick Reference: Model Quality Checklist
| Area |
Best Practice |
| Tables |
Clear dimension vs fact classification |
| Naming |
Human-readable: Customer Name not CUST_NM |
| Descriptions |
All tables, columns, measures documented |
| Measures |
Explicit DAX measures for business metrics |
| Relationships |
One-to-many from dimension to fact |
| Cross-filter |
Single direction unless specifically needed |
| Hidden fields |
Hide technical keys, IDs from report view |
| Date table |
Dedicated marked date table |
MCP Tools Reference
Use these Power BI Modelling MCP operations:
| Operation Category |
Key Operations |
connection_operations |
Connect, ListConnections, ListLocalInstances, ConnectFabric |
model_operations |
Get, GetStats, ExportTMDL |
table_operations |
List, Get, Create, Update, GetSchema |
column_operations |
List, Get, Create, Update (descriptions, hidden, format) |
measure_operations |
List, Get, Create, Update, Move |
relationship_operations |
List, Get, Create, Update, Activate, Deactivate |
dax_query_operations |
Execute, Validate |
calculation_group_operations |
List, Create, Update |
security_role_operations |
List, Create, Update, GetEffectivePermissions |
Common Tasks
Add Measure with Description
measure_operations(
operation: "Create",
definitions: [{
name: "Total Sales",
tableName: "Sales",
expression: "SUM(Sales[Amount])",
formatString: "$#,##0",
description: "Sum of all sales amounts"
}]
)
Update Column Description
column_operations(
operation: "Update",
definitions: [{
tableName: "Customer",
name: "CustomerKey",
description: "Unique identifier for customer dimension",
isHidden: true
}]
)
Create Relationship
relationship_operations(
operation: "Create",
definitions: [{
fromTable: "Sales",
fromColumn: "CustomerKey",
toTable: "Customer",
toColumn: "CustomerKey",
crossFilteringBehavior: "OneDirection"
}]
)
When to Use Microsoft Learn MCP
Research current best practices using microsoft_docs_search for:
- Latest DAX function documentation
- New Power BI features and capabilities
- Complex modelling scenarios (SCD Type 2, many-to-many)
- Performance optimisation techniques
- Security implementation patterns
1---2name: powerbi-modelling3description: Power BI semantic modelling assistant for building optimised data models. Use when working with Power BI semantic models, creating measures, designing star schemas, configuring relationships, implementing RLS, or optimising model performance. Triggers on queries about DAX calculations, table relationships, dimension/fact table design, naming conventions, model documentation, cardinality, cross-filter direction, calculation groups, and data model best practices. Always connects to the active model first using power-bi-modelling MCP tools to understand the data structure before providing guidance.4---56# Power BI Semantic Modelling78Guide users in building optimised, well-documented Power BI semantic models following Microsoft best practices.910## When to Use This Skill1112Use this skill when users ask about:13- Creating or optimising Power BI semantic models14- Designing star schemas (dimension/fact tables)15- Writing DAX measures or calculated columns16- Configuring table relationships (cardinality, cross-filter)17- Implementing row-level security (RLS)18- Naming conventions for tables, columns, measures19- Adding descriptions and documentation to models20- Performance tuning and optimisation21- Calculation groups and field parameters22- Model validation and best practice checks2324**Trigger phrases:** "create a measure", "add relationship", "star schema", "optimise model", "DAX formula", "RLS", "naming convention", "model documentation", "cardinality", "cross-filter"2526## Prerequisites2728### Required Tools29- **Power BI Modelling MCP Server**: Required for connecting to and modifying semantic models30 - Enables: connection_operations, table_operations, measure_operations, relationship_operations, etc.31 - Must be configured and running to interact with models3233### Optional Dependencies34- **Microsoft Learn MCP Server**: Recommended for researching latest best practices35 - Enables: microsoft_docs_search, microsoft_docs_fetch36 - Use for complex scenarios, new features, and official documentation3738## Workflow3940### 1. Connect and Analyse First4142Before providing any modelling guidance, always examine the current model state:4344```451. List connections: connection_operations(operation: "ListConnections")462. If no connection, check for local instances: connection_operations(operation: "ListLocalInstances")473. Connect to the model (Desktop or Fabric)484. Get model overview: model_operations(operation: "Get")495. List tables: table_operations(operation: "List")506. List relationships: relationship_operations(operation: "List")517. List measures: measure_operations(operation: "List")52```5354### 2. Evaluate Model Health5556After connecting, assess the model against best practices:5758- **Star Schema**: Are tables properly classified as dimension or fact?59- **Relationships**: Correct cardinality? Minimal bidirectional filters?60- **Naming**: Human-readable, consistent naming conventions?61- **Documentation**: Do tables, columns, measures have descriptions?62- **Measures**: Explicit measures for key calculations?63- **Hidden Fields**: Are technical columns hidden from report view?6465### 3. Provide Targeted Guidance6667Based on analysis, guide improvements using references:68- Star schema design: See [star-schema.md](references/star-schema.md)69- Relationship configuration: See [relationships.md](references/relationships.md)70- DAX measures and naming: See [measures-dax.md](references/measures-dax.md)71- Performance optimisation: See [performance.md](references/performance.md)72- Row-level security: See [rls.md](references/rls.md)7374## Quick Reference: Model Quality Checklist7576| Area | Best Practice |77|------|--------------|78| Tables | Clear dimension vs fact classification |79| Naming | Human-readable: `Customer Name` not `CUST_NM` |80| Descriptions | All tables, columns, measures documented |81| Measures | Explicit DAX measures for business metrics |82| Relationships | One-to-many from dimension to fact |83| Cross-filter | Single direction unless specifically needed |84| Hidden fields | Hide technical keys, IDs from report view |85| Date table | Dedicated marked date table |8687## MCP Tools Reference8889Use these Power BI Modelling MCP operations:9091| Operation Category | Key Operations |92|-------------------|----------------|93| `connection_operations` | Connect, ListConnections, ListLocalInstances, ConnectFabric |94| `model_operations` | Get, GetStats, ExportTMDL |95| `table_operations` | List, Get, Create, Update, GetSchema |96| `column_operations` | List, Get, Create, Update (descriptions, hidden, format) |97| `measure_operations` | List, Get, Create, Update, Move |98| `relationship_operations` | List, Get, Create, Update, Activate, Deactivate |99| `dax_query_operations` | Execute, Validate |100| `calculation_group_operations` | List, Create, Update |101| `security_role_operations` | List, Create, Update, GetEffectivePermissions |102103## Common Tasks104105### Add Measure with Description106```107measure_operations(108 operation: "Create",109 definitions: [{110 name: "Total Sales",111 tableName: "Sales",112 expression: "SUM(Sales[Amount])",113 formatString: "$#,##0",114 description: "Sum of all sales amounts"115 }]116)117```118119### Update Column Description120```121column_operations(122 operation: "Update",123 definitions: [{124 tableName: "Customer",125 name: "CustomerKey",126 description: "Unique identifier for customer dimension",127 isHidden: true128 }]129)130```131132### Create Relationship133```134relationship_operations(135 operation: "Create",136 definitions: [{137 fromTable: "Sales",138 fromColumn: "CustomerKey",139 toTable: "Customer",140 toColumn: "CustomerKey",141 crossFilteringBehavior: "OneDirection"142 }]143)144```145146## When to Use Microsoft Learn MCP147148Research current best practices using `microsoft_docs_search` for:149- Latest DAX function documentation150- New Power BI features and capabilities151- Complex modelling scenarios (SCD Type 2, many-to-many)152- Performance optimisation techniques153- Security implementation patterns