Adding Debugging and references as we ran out of space.

Debugging

For debugging, it is recommended to validate the following for the expected answer measure:

• Measure is not hidden
• Measure is included in Q&A
• Measure has relevant unique synonyms added

This ensures that Copilot returns the correct measures in response to queries.

References

Some references that will help you do some modelling best practices and copilot best practices to improve your experience.

Linguistic Modelling:

- Get better results from #PowerBI Copilot (crossjoin.co.uk)

- Tuning Power BI Copilot with Row Labels and Key Columns (crossjoin.co.uk)

- Ask Copilot for data from your model — Power BI | Microsoft Learn

- Intro to Q&A tooling to train Power BI Q&A (preview) — Power BI | Microsoft Learn

- Edit Q&A linguistic schema and add phrasings in Power BI Desktop — Power BI | Microsoft Learn

- Chris Webb’s BI Blog: Naming Tables, Columns And Measures In Power BI (crossjoin.co.uk)

- Natural Language for Power BI — YouTube

Semantic Modelling:

- Understand star schema and the importance for Power BI — Power BI | Microsoft Learn

- Data modelling guidance

- Update your data model to work well with Copilot for Power BI — Power BI | Microsoft Learn

- Chris Webb’s BI Blog: Five Mistakes To Avoid When Migrating To Power BI From Another BI Platform (crossjoin.co.uk)

- Validate semantic model relationships — Tabular Editor Blog

- Best Practice Analyzer Improvements | Tabular Editor Documentation

- Analysis-Services/BestPracticeRules at master · microsoft/Analysis-Services · GitHub

- Best practice rules to improve your model’s performance | Microsoft Power BI Blog | Microsoft Power BI