Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

Next up in the FabCon + SQLCon recap series: The roadmap for Microsoft SQL and Maximizing Developer experiences in Fabric. All sessions are available on-demand after the live show. Register now

Reply
Ar_Sh
Advocate II
Advocate II

Need Help

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?

2 ACCEPTED SOLUTIONS
Shubham_rai955
Super User
Super User

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.

1. Base measure

 
Sales Amount := SUM ( Sales[Amount] )

2. Campaign Sales measure using TREATAS

 
Campaign Sales := CALCULATE ( [Sales Amount], TREATAS ( VALUES ( CampaignMapping[CustomerID] ), Customers[CustomerID] ), TREATAS ( VALUES ( CampaignMapping[ProductCategory] ), Products[Category] ) )

3. Explanation 

  • 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.

View solution in original post

cengizhanarslan
Super User
Super User

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] )
)
_________________________________________________________
If this helped, ✓ Mark as Solution | Kudos appreciated
Connect on LinkedIn | Follow on Medium
AI-assisted tools are used solely for wording support. All conclusions are independently reviewed.

View solution in original post

3 REPLIES 3
cengizhanarslan
Super User
Super User

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] )
)
_________________________________________________________
If this helped, ✓ Mark as Solution | Kudos appreciated
Connect on LinkedIn | Follow on Medium
AI-assisted tools are used solely for wording support. All conclusions are independently reviewed.
anilelmastasi
Super User
Super User

My advice is creating a CampaignBridge table at the same grain as Sales.

 

Shubham_rai955
Super User
Super User

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.

1. Base measure

 
Sales Amount := SUM ( Sales[Amount] )

2. Campaign Sales measure using TREATAS

 
Campaign Sales := CALCULATE ( [Sales Amount], TREATAS ( VALUES ( CampaignMapping[CustomerID] ), Customers[CustomerID] ), TREATAS ( VALUES ( CampaignMapping[ProductCategory] ), Products[Category] ) )

3. Explanation 

  • 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.

Helpful resources

Announcements
New to Fabric survey Carousel

New to Fabric Survey

If you have recently started exploring Fabric, we'd love to hear how it's going. Your feedback can help with product improvements.

Power BI DataViz World Championships carousel

Power BI DataViz World Championships - June 2026

A new Power BI DataViz World Championship is coming this June! Don't miss out on submitting your entry.

Join our Fabric User Panel

Join our Fabric User Panel

Share feedback directly with Fabric product managers, participate in targeted research studies and influence the Fabric roadmap.

March Power BI Update Carousel

Power BI Community Update - March 2026

Check out the March 2026 Power BI update to learn about new features.