Composite models in Power BI - Step-by-Step Guide
ImportDisabledActivePractice
What is the main benefit of using composite models in Power BI?
Solution
Step 1: Understand composite models purpose
Composite models let you combine data from different sources in one Power BI report.Step 2: Compare options
Only 'They allow combining data from multiple sources in one report.' correctly states this benefit; others are incorrect or unrelated.Final Answer:
They allow combining data from multiple sources in one report. -> Option BQuick Check:
Composite models = combine multiple sources [OK]
- Thinking composite models only work with Import mode
- Believing composite models clean data automatically
- Assuming relationships are not needed in composite models
Which of the following is the correct way to enable composite models in Power BI?
Options > Preview Features > Enable Composite Models
Solution
Step 1: Locate composite models setting
Composite models are enabled via Options > Preview Features in Power BI Desktop.Step 2: Verify other options
Other options do not contain this setting, so only Enable Composite Models under Options > Preview Features is correct.Final Answer:
Enable Composite Models under Options > Preview Features -> Option AQuick Check:
Composite models setting = Options > Preview Features [OK]
- Looking for composite models in Export or Themes menus
- Confusing data transformation with enabling composite models
- Assuming composite models are enabled by default
Given a composite model with two tables: Sales (Import mode) and Customers (DirectQuery mode), what happens when you create a relationship between them?
Solution
Step 1: Understand composite model relationships
Composite models allow relationships between Import and DirectQuery tables.Step 2: Analyze options
Only 'Power BI allows cross-source relationships, enabling combined filtering and analysis.' correctly states what happens; others are false.Final Answer:
Power BI allows cross-source relationships, enabling combined filtering and analysis. -> Option DQuick Check:
Composite models = cross-source relationships allowed [OK]
- Believing relationships cannot connect different storage modes
- Thinking DirectQuery tables lose their mode when related
- Assuming relationships only work within same storage mode
You created a composite model with Import and DirectQuery tables but get an error when trying to build a relationship. What is a likely cause?
Solution
Step 1: Check composite models feature status
If composite models are not enabled in Preview Features, relationships between Import and DirectQuery tables cause errors.Step 2: Evaluate other options
DAX syntax is not used to create relationships; Power BI supports relationships; same database does not cause errors.Final Answer:
The composite models feature is not enabled in Preview Features. -> Option AQuick Check:
Enable composite models to allow cross-source relationships [OK]
- Trying to fix relationships with DAX syntax
- Assuming relationships are unsupported in Power BI
- Thinking same database causes relationship errors
You have a composite model with three tables: Orders (Import), Products (DirectQuery), and Customers (Import). You want to create a report showing total sales by product category and customer region. Which approach is best?
Solution
Step 1: Understand composite model usage
Composite models allow mixing Import and DirectQuery tables with relationships for combined analysis.Step 2: Apply to scenario
Creating relationships between all tables and using DirectQuery forProductsenables combined sales by product category and customer region.Step 3: Evaluate other options
Importing all tables may not be possible; ignoring tables loses insights; separate reports reduce integration.Final Answer:
Create relationships between all tables, use DirectQuery forProducts, and build visuals combining all data. -> Option CQuick Check:
Composite models + relationships = combined report [OK]
- Trying to avoid composite models by importing all data
- Ignoring important tables for simplicity
- Splitting data into separate reports unnecessarily
Ready to prove it?
Pass the test and this pattern moves unknown
