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!Get Fabric certified for FREE! Don't miss your chance! Learn more
Hi All,
Thanks in advance,I tried with disconnected Date table but not getting what we want
Hi @sanjaymithran , Hope you're doing okay! May we know if it worked for you, or are you still experiencing difficulties? Let us know — your feedback can really help others in the same situation.
Hi @sanjaymithran , hope you are doing great. May we know if your issue is solved or if you are still experiencing difficulties. Please share the details as it will help the community, especially others with similar issues.
You can solve this by using two disconnected slicer tables and the TREATAS function. Each slicer needs its own table so that it only controls one measure.
Steps:
Slicer1 = DISTINCT(SELECTCOLUMNS(Data, "Quarter", Data[Slicer1]))
Slicer2 = DISTINCT(SELECTCOLUMNS(Data, "Quarter", Data[Slicer2]))
Sales1 =
CALCULATE(
SUM(Data[sales]),
TREATAS(VALUES(Slicer1[Quarter]), Data[Slicer1])
)
Sales2 =
CALCULATE(
SUM(Data[sales]),
TREATAS(VALUES(Slicer2[Quarter]), Data[Slicer2])
)
Example:
That should give you the exact results you were expecting.
You can solve this by using two disconnected slicer tables and Treatas. Each slicer needs its own table so that it only controls one measure.
Steps:
Slicer1 = DISTINCT(SELECTCOLUMNS(Data, "Quarter", Data[Slicer1])) Slicer2 = DISTINCT(SELECTCOLUMNS(Data, "Quarter", Data[Slicer2]))
Sales1 =
CALCULATE(
SUM(Data[sales]),
TREATAS(VALUES(Slicer1[Quarter]), Data[Slicer1])
)
Sales2 =
CALCULATE(
SUM(Data[sales]),
TREATAS(VALUES(Slicer2[Quarter]), Data[Slicer2])
)Example:
That should give you the exact results you were expecting.
@Naman01 Need to apply some static filters in the calculation
Sales1 =
CALCULATE(
SUM(Data[sales]),
TREATAS(VALUES(Slicer1[Quarter]), Data[Slicer1])
)
Sales1- Type =Actual and ProdGroup=Term
Sales2 is diffrent
Hi @sanjaymithran , Thank you for reaching out to the Microsoft Community Forum.
You don’t need to change your slicers, model or interactions. Your setup with disconnected slicers and TREATAS is already correct. To apply static filters (like Type and ProdGroup), just add them as additional filter arguments inside CALCULATE. DAX will combine the slicer filter (via TREATAS) and your fixed filters in the same filter context.
For example:
Sales1 =
CALCULATE(
SUM(Data[sales]),
TREATAS(VALUES(Slicer1[Quarter]), Data[Quarter]),
Data[Type] = "Actual",
Data[ProdGroup] = "Term"
)
Sales2 =
CALCULATE(
SUM(Data[sales]),
TREATAS(VALUES(Slicer2[Quarter]), Data[Quarter]),
Data[Type] = "Forecast"
)
This keeps each slicer independent while still enforcing your static conditions. Avoid using SELECTEDVALUE comparisons on the fact column (like Dataset[QuarterYear] = SELECTEDVALUE(...)) because that creates a weaker scalar filter and can break context. TREATAS is the correct approach here since it creates a proper virtual relationship to your data grain.
Hi @v-hashadapu ,
Thanks for your reply,I used below calculation but performance is very poor,is TREATAS will give better performance?
Sales1 =
CALCULATE(
SUM(Data[sales]),
FILTER('Data',Data[ProdGroup] = "Term"
&& Data[Type] = "Actual"
&& CONTAINS(VALUES(DateSlicer1),Slicer1[Quarter],Data[Quarter]))
)
Thanks,
One disconnected table should be enough. The other one should be a related table. Both though must include the quarter information. Since you're trying to show 0 if the value is blank as in the case of dv2 Sales1 on Table 1, you must also use a separate dimension table for dim column - you cannot assign a value to a row that doesnt exist - there is no dv2 Q1 2025 in your data.
Your relationships should look like below
Both Slicer 1 and 2 tables would be as below:
Add (or subtract) 0 to your sales measure to force 0 when the value is blank
Sales1 =
SUM('Table'[sales]) + 0
Sales2 =
--TREATAS to use a virtual relationship since Slicer2 is not related to your other tables
CALCULATE (
[Sales1],
TREATAS ( VALUES ( Slicer2[createdate] ), Slicer1[createdate] )
)
+ 0
Create another measure as a visual filter to hide rows where Sales 1 and 2 are both zero
Filter =
IF ( [Sales1] = 0 && [Sales2] = 0, 0, 1 )
Please see the attached pbix.
Hi @sanjaymithran
1. Create calcualted col for year - qtr
2. Then Create two disconnected slicer table
3. Then create two measures
I have attached the pbix for you reference
If this answers your question, kindly accept it as a solution and give kudos.
Thanks, need to apply filter in sales1 and sales2 measures example
Sales1 :=
CALCULATE(
SUM ( Fact[sales] ),
KEEPFILTERS(
TREATAS(
VALUES( Slicer1_Quarter[YearQuarter] ),
DimDate[YearQuarter]
)
)
)
Sales2 :=
CALCULATE(
SUM ( Fact[sales] ),
KEEPFILTERS(
TREATAS(
VALUES( Slicer2_Quarter[YearQuarter] ),
DimDate[YearQuarter]
)
)
)
Hi @sanjaymithran,
You can try this:
Create 2 small tables with just your quarter names (Q1 2025, Q2 2025, etc.), don't link them to anything in your model. These are just for the slicers.
Then 2 simple measures:
Sales1 = CALCULATE( SUM(FactSales[sales]), TREATAS(VALUES(Slicer1[Quarter]), DimDate[Quarter]) )
Sales2 = CALCULATE( SUM(FactSales[sales]), TREATAS(VALUES(Slicer2[Quarter]), DimDate[Quarter]) )
In your visual: Put dim1 on rows, Sales1 and Sales2 as values. Add 2 separate slicers, one for each quarter table.
Now you can pick Q1 in one slicer and Q4 in the other, each measure respects its own slicer!
TREATAS is doing the magic here, it tells each measure which quarter to use from your actual date table.
Thanks in advance and kudos if this helps!
Thanks QuentinGa,what the logic for DimDate[Quarter]? tried below logic not workout
Hi @sanjaymithran,
can you please clarify what you are asking?
If this helped, please consider giving kudos and mark as a solution
@me in replies or I'll lose your thread
Want to check your DAX skills? Answer my biweekly DAX challenges on the kubisco Linkedin page
Consider voting this Power BI idea
Francesco Bergamaschi
MBA, M.Eng, M.Econ, Professor of BI
Share feedback directly with Fabric product managers, participate in targeted research studies and influence the Fabric roadmap.
Check out the February 2026 Power BI update to learn about new features.
| User | Count |
|---|---|
| 68 | |
| 59 | |
| 48 | |
| 20 | |
| 16 |
| User | Count |
|---|---|
| 107 | |
| 106 | |
| 39 | |
| 27 | |
| 27 |