Imagine you want to create a sales report that combines data from your online store and your physical store. Why would you use multiple data sources in one Power BI report?
Think about why combining data from different places helps you see the full picture.
Using multiple data sources lets you bring together data from different systems, like online and physical stores, so you can analyze all sales in one place.
You have two tables: OnlineSales and StoreSales. Both have a column Amount. You want a measure that sums sales from both sources. Which DAX measure gives the correct total sales?
Think about how to add sums from two separate tables.
Option A correctly sums each table's Amount column separately and adds the results. Option A tries to sum columns from different tables inside SUM, which is invalid. Option A misuses CALCULATE. Option A uses SUMX but misses table references properly.
You want to show monthly sales from OnlineSales and StoreSales side by side for easy comparison. Which visualization type is best?
Think about how to compare two categories side by side for each month.
A clustered column chart shows separate bars for each sales source side by side per month, making comparison easy. Stacked columns combine values, hiding individual source amounts. Pie charts do not show time trends. Line charts combine sources, not showing separate values clearly.
You have two data sources: OnlineSales and StoreSales. Both have a ProductID column. You also have a Products table. How should you model relationships to analyze sales by product?
Think about how product details relate to many sales records.
Products is a lookup table with unique ProductID values. Sales tables have many rows per product. So, one-to-many relationships from Products to each sales table on ProductID are correct. Many-to-many or one-to-one are incorrect here. Using LOOKUPVALUE is less efficient and unnecessary with proper relationships.
You wrote this DAX measure to sum sales from two sources:
Total Sales = SUM(OnlineSales[Amount]) + SUM(StoreSales[Amount])
But the total is double what you expect when filtering by product. What is the likely cause?
Think about how relationships affect filtering and totals.
If both sales tables relate to Products with many-to-many or ambiguous relationships, filtering by product can cause double counting. The measure syntax is correct. Text values would cause errors, not double totals. Missing date filters would not cause doubling.