Scenario Mode

👤 Your Role: You are a Power BI developer at a retail company.

📋 Request: Your manager wants you to create clear documentation standards for all Power BI reports and dashboards to ensure easy understanding and maintenance by the team.

📊 Data: You have access to existing Power BI reports with various measures, visuals, and data sources but no consistent documentation.

🎯 Deliverable: A set of documentation standards including naming conventions, descriptions for measures and visuals, and guidelines for report layout and comments.

Progress0 / 6 steps

Sample Data

Report Name	Measure Name	Measure Formula	Visual Type	Data Source
Sales Overview	Total Sales	=SUM(Sales[Amount])	Card	Sales Table
Sales Overview	Sales Growth %	=DIVIDE([Total Sales]-[Total Sales LY],[Total Sales LY])	Line Chart	Sales Table
Customer Insights	New Customers	=CALCULATE(DISTINCTCOUNT(Customers[CustomerID]), Customers[FirstPurchaseYear]=YEAR(TODAY()))	Bar Chart	Customers Table
Customer Insights	Customer Retention Rate	=DIVIDE([Returning Customers],[Total Customers])	Gauge	Customers Table
Inventory Status	Stock Level	=SUM(Inventory[Quantity])	Table	Inventory Table
Inventory Status	Stock Out %	=DIVIDE(CALCULATE(COUNTROWS(Inventory), Inventory[Quantity]=0), COUNTROWS(Inventory))	Pie Chart	Inventory Table

1

Step 1: Define a naming convention for measures and visuals.

Use PascalCase for measure names (e.g., TotalSales, SalesGrowthPercent). Prefix visual names with their type and purpose (e.g., Card_TotalSales, Chart_SalesGrowth).

Expected Result

2

Step 2: Add detailed descriptions for each measure in Power BI.

In the measure properties, add a description explaining what the measure calculates and any important details (e.g., 'TotalSales: Sum of all sales amounts from the Sales table').

Expected Result

3

Step 3: Document data sources and relationships in the report.

Create a dedicated page or section in the report describing each data source, its refresh frequency, and key relationships.

Expected Result

4

Step 4: Use consistent layout and grouping for visuals.

Group related visuals together with clear titles and use consistent colors and fonts across pages.

Expected Result

5

Step 5: Add comments in DAX formulas where complex logic is used.

Use double dashes (--) to add comments inside DAX measures explaining the logic step-by-step.

Expected Result

6

Step 6: Create a documentation template for new reports.

Include sections for report purpose, data sources, measure definitions, visual descriptions, and update history.

Expected Result

Final Result

-----------------------------------------
| Power BI Documentation Standards Guide |
-----------------------------------------

1. Naming Conventions:
   - Measures: PascalCase (e.g., TotalSales)
   - Visuals: Prefix with type (e.g., Card_TotalSales)

2. Measure Descriptions:
   - Add clear, concise explanations in measure properties.

3. Data Source Documentation:
   - List all sources, refresh schedules, and relationships.

4. Report Layout:
   - Group related visuals, consistent colors and fonts.

5. DAX Comments:
   - Use -- comments for complex formulas.

6. Documentation Template:
   - Sections for purpose, data, measures, visuals, updates.

-----------------------------------------

✓Consistent naming improves report clarity and maintenance.

✓Descriptions help non-technical users understand measures.

✓Documenting data sources prevents confusion about data origins.

✓Standard layouts enhance user experience and navigation.

✓Comments in formulas reduce onboarding time for new developers.

✓A documentation template ensures uniformity across reports.

Bonus Challenge

Create a Power BI report page that automatically displays documentation details for all measures and visuals using DAX and report tooltips.

Show Hint