Join us at FabCon Atlanta from March 16 - 20, 2026, for the ultimate Fabric, Power BI, AI and SQL community-led event. Save $200 with code FABCOMM.
Register now!The Power BI Data Visualization World Championships is back! Get ahead of the game and start preparing now! Learn more
I have a disconnected CampaignMapping table with columns (CampaignName, CustomerID, ProductCategory) where the granularity is a many-to-many combination, while Sales is at the Order/Product level related only to standard dimensions (Customers, Products, Date).
This granularity mismatch makes physical relationships impossible. How can I write a Campaign Sales measure in DAX so that selecting CampaignName on a slicer virtually filters Sales by both CustomerID and ProductCategory matches?
Solved! Go to Solution.
You can create a Campaign Sales measure by building a virtual relationship from the disconnected CampaignMapping table to Sales using TREATAS on both CustomerID and ProductCategory.
VALUES(CampaignMapping[CustomerID]) returns the distinct customers for the currently selected campaign(s).
The first TREATAS tells the engine to treat those values as if they came from Customers[CustomerID], so the row context on Sales is filtered by matching customers.
The second TREATAS does the same for ProductCategory → Products[Category], so only Sales rows where both customer and category match the campaign remain.
Because TREATAS creates a virtual relationship instead of a physical one, it works even though the CampaignMapping granularity (Campaign–Customer–Category) does not match the Sales fact granularity.
Please check the formula below:
Campaign Sales =
VAR SelectedCustomers =
VALUES ( CampaignMapping[CustomerID] )
VAR SelectedCategories =
VALUES ( CampaignMapping[ProductCategory] )
RETURN
CALCULATE (
[Total Sales],
TREATAS ( SelectedCustomers, Customers[CustomerID] ),
TREATAS ( SelectedCategories, Products[ProductCategory] )
)
Please check the formula below:
Campaign Sales =
VAR SelectedCustomers =
VALUES ( CampaignMapping[CustomerID] )
VAR SelectedCategories =
VALUES ( CampaignMapping[ProductCategory] )
RETURN
CALCULATE (
[Total Sales],
TREATAS ( SelectedCustomers, Customers[CustomerID] ),
TREATAS ( SelectedCategories, Products[ProductCategory] )
)
My advice is creating a CampaignBridge table at the same grain as Sales.
You can create a Campaign Sales measure by building a virtual relationship from the disconnected CampaignMapping table to Sales using TREATAS on both CustomerID and ProductCategory.
VALUES(CampaignMapping[CustomerID]) returns the distinct customers for the currently selected campaign(s).
The first TREATAS tells the engine to treat those values as if they came from Customers[CustomerID], so the row context on Sales is filtered by matching customers.
The second TREATAS does the same for ProductCategory → Products[Category], so only Sales rows where both customer and category match the campaign remain.
Because TREATAS creates a virtual relationship instead of a physical one, it works even though the CampaignMapping granularity (Campaign–Customer–Category) does not match the Sales fact granularity.
The Power BI Data Visualization World Championships is back! Get ahead of the game and start preparing now!
| User | Count |
|---|---|
| 19 | |
| 13 | |
| 10 | |
| 4 | |
| 4 |
| User | Count |
|---|---|
| 31 | |
| 28 | |
| 19 | |
| 11 | |
| 10 |