Multiple data sources in one report in Power BI - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to load data from two different sources in Power BI.

Power BI

Source1 = Sql.Database("ServerName", [1])

Drag options to blanks, or click blank then click option'

A"ServerName"

B"Table1"

C"DataSource1"

D"Database1"

Attempts:

3 left

💡 Hint

Common Mistakes

Using the table name instead of the database name.

Repeating the server name twice.

In Power BI, to connect to a SQL Server database, you specify the database name as the second argument in Sql.Database.

2fill in blank

medium

Complete the code to merge two tables from different data sources in Power BI.

Power BI

MergedTable = Table.NestedJoin(Source1, {"ID"}, [1], {"ID"}, "NewTable")

Drag options to blanks, or click blank then click option'

ASource2

BSource1

CSource3

DSource4

Attempts:

3 left

💡 Hint

Common Mistakes

Joining the same source to itself.

Using a source that is not loaded.

To merge tables from two different sources, you join Source1 with Source2 on the common column.

3fill in blank

hard

Fix the error in the DAX measure to calculate total sales from two different tables.

Power BI

TotalSales = SUM([1][SalesAmount]) + SUM(Source2[SalesAmount])

Drag options to blanks, or click blank then click option'

ASource1

BSource3

CSource4

DSource5

Attempts:

3 left

💡 Hint

Common Mistakes

Using a table name that does not exist.

Misspelling the table name.

The measure must sum the SalesAmount column from both Source1 and Source2 tables.

4fill in blank

hard

Fill both blanks to create a relationship between two tables from different sources in Power BI.

Power BI

Relationship = Table.AddRelationship([1], "CustomerID", [2], "CustomerID")

Drag options to blanks, or click blank then click option'

ASource1

BSource2

CSource3

DSource4

Attempts:

3 left

💡 Hint

Common Mistakes

Swapping the tables in the relationship.

Using tables that do not share the key.

To relate two tables, specify the first table and the second table with the common key column.

5fill in blank

hard

Fill all three blanks to create a calculated table combining data from two sources with a filter.

Power BI

CombinedTable = FILTER(UNION([1], [2]), [3] > 1000)

Drag options to blanks, or click blank then click option'

ASource1

BSource2

CSalesAmount

DCustomerID

Attempts:

3 left

💡 Hint

Common Mistakes

Using a column name instead of a table name in the first two blanks.

Filtering on a column not present in the combined table.

The UNION combines two tables, and FILTER applies a condition on the SalesAmount column.

Practice

1. What is the main benefit of using multiple data sources in one Power BI report?

easy

A. You can combine different types of data for richer insights.

B. It automatically cleans all data without user input.

C. It limits the report to only one data table.

D. It removes the need for relationships between tables.

Solution

1. Step 1: Understand the purpose of multiple data sources

   Multiple data sources allow combining different datasets to get a fuller picture.

2. Step 2: Identify the benefit in report insights

   Combining data from various sources enriches the analysis and insights.

3. Final Answer:

   You can combine different types of data for richer insights. -> Option A

4. Quick Check:

   Multiple data sources = richer insights [OK]

Hint: Multiple sources mean combining data for better insights [OK]

Common Mistakes:

• Thinking multiple sources clean data automatically
• Believing multiple sources limit data to one table
• Assuming relationships are not needed

2. Which of the following is the correct way to add a new data source in Power BI Desktop?

easy

A. Right-click on a visual and select Add Data Source

B. Use the Modeling tab to create a new data source

C. Go to Home tab > Get Data > Choose source > Load

D. Drag and drop files directly onto the report canvas

Solution

1. Step 1: Recall the process to add data

   In Power BI Desktop, new data sources are added via Home tab's Get Data option.

2. Step 2: Confirm the correct menu and steps

   Choose the source type and then load the data into the report.

3. Final Answer:

   Go to Home tab > Get Data > Choose source > Load -> Option C

4. Quick Check:

   Get Data on Home tab = add source [OK]

Hint: Use Home > Get Data to add sources [OK]

Common Mistakes:

• Trying to add data from the Modeling tab
• Right-clicking visuals to add data
• Dragging files onto the canvas doesn't load data

3. Given two tables from different data sources: Sales and Products, which DAX formula correctly calculates total sales amount by product category assuming a relationship exists?

medium

A. Total Sales = SUM(Sales[Amount])

B. Total Sales = CALCULATE(SUM(Sales[Amount]), Products[Category])

C. Total Sales = SUMX(Products, RELATED(Sales[Amount]))

D. Total Sales = SUMX(Products, SUM(Sales[Amount]))

Solution

1. Step 1: Understand the relationship usage

   With a relationship between Sales and Products, SUM(Sales[Amount]) aggregates sales correctly by category in visuals.

2. Step 2: Evaluate each formula

   Total Sales = SUM(Sales[Amount]) sums Sales amount directly, which works with relationships. Total Sales = CALCULATE(SUM(Sales[Amount]), Products[Category]) syntax is invalid. Total Sales = SUMX(Products, RELATED(Sales[Amount])) misuses RELATED. Total Sales = SUMX(Products, SUM(Sales[Amount])) incorrectly sums the grand total for each product row, inflating results.

3. Final Answer:

   Total Sales = SUM(Sales[Amount]) -> Option A

4. Quick Check:

   SUM with relationships = correct total [OK]

Hint: Use SUM on sales column when relationships exist [OK]

Common Mistakes:

• Using CALCULATE without filter expression
• Misusing RELATED in SUMX
• Overcomplicating simple SUM aggregation

4. You imported two data sources but your report shows no combined data. What is the most likely issue?

medium

A. You added too many visuals on the report page.

B. You did not refresh the data after import.

C. You used the wrong file format for import.

D. You forgot to create relationships between tables.

Solution

1. Step 1: Identify why combined data is missing

   Without relationships, tables from different sources cannot connect, so combined data won't show.

2. Step 2: Check other options

   Refreshing data or file format issues usually cause errors, not missing combined data. Too many visuals do not affect data combination.

3. Final Answer:

   You forgot to create relationships between tables. -> Option D

4. Quick Check:

   Missing relationships = no combined data [OK]

Hint: Create relationships to combine data sources [OK]

Common Mistakes:

• Ignoring relationships after importing data
• Assuming refresh fixes missing relationships
• Blaming visuals for data connection issues

5. You have sales data from Excel and customer data from SQL Server. You want to create a report showing total sales per customer region. How should you combine these sources effectively?

hard

A. Create separate reports for each source and link them with bookmarks.

B. Load both sources, create a relationship between customer IDs, then build visuals using fields from both tables.

C. Load only the sales data and manually type customer regions in Power BI.

D. Merge the Excel and SQL tables into one before loading into Power BI.

Solution

1. Step 1: Load both data sources separately

   Import Excel sales data and SQL customer data into Power BI as separate tables.

2. Step 2: Create a relationship between customer IDs

   Link the tables on customer ID to connect sales with customer regions.

3. Step 3: Build visuals using fields from both tables

   Use the relationship to show total sales by customer region in one report.

4. Final Answer:

   Load both sources, create a relationship between customer IDs, then build visuals using fields from both tables. -> Option B

5. Quick Check:

   Separate sources + relationship + visuals = combined report [OK]

Hint: Load sources, relate keys, then build combined visuals [OK]

Common Mistakes:

• Trying to merge tables outside Power BI unnecessarily
• Ignoring relationships and typing data manually
• Splitting data into separate reports instead of combining