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 during Fabric Data Days. Don't miss your chance! Request now
I'm encountering an issue in Power BI where the Marketplace slicer does not show any selectable options when I filter two non-overlapping date ranges.
Even though data for the marketplaces exists in the underlying table, the slicer becomes empty unless the selected date ranges overlap. It seems that when two separate time filters are applied, the marketplace slicer cannot resolve any valid entries due to the lack of shared dates.
This behavior is affecting the usability of the report, as users cannot explore different time windows in comparison without losing the ability to filter by marketplace.
Could you please assist in identifying a fix or a recommended modeling approach to ensure that the marketplace filter remains functional when comparing disjoint time periods? Thanks
Solved! Go to Solution.
Hi @Simomazzi The problem might be because the marketplace slicer relies on overlapping date ranges to display options. To fix this, use independent date filters with disconnected date tables or combine the date ranges in the model. You can also adjust the slicer logic to not directly depend on the date filters.
Hi @Simomazzi ,
I wanted to follow up and see if you’ve had a chance to review the information provided here.
If any of the responses helped solve your issue, please consider marking it "Accept as Solution" and giving it a 'Kudos' to help others easily find it.
Let me know if you have any further questions!
Hi @Simomazzi , Thank you for reaching out to the Microsoft Community Forum.
This happens because Power BI tries to find data that matches both date ranges at once, which isn’t possible when they don’t overlap, leaving your slicer empty. create a disconnected date table to handle your date range slicers. Don’t connect this table to your fact table. This keeps the date selections independent. This table won’t link directly to your data, which prevents the filtering issue. Example:
DisconnectedDate = CALENDAR(DATE(2020, 1, 1), DATE(2025, 12, 31))
Next, add two slicers to your report, both using DisconnectedDate[Date]. Label them something like “Date Range 1” and “Date Range 2” and set them to Between mode for easy range selection. These slicers will let users pick the time periods they want to compare, like January 2023 and June 2023. Now, create measures to calculate your metric for each date range. Use TREATAS to apply the slicer selections without messing up other filters. Example:
Sales_DateRange1 =
CALCULATE(
SUM(Sales[Amount]),
TREATAS(VALUES(DisconnectedDate[Date]), Sales[Date])
)
Sales_DateRange2 =
CALCULATE(
SUM(Sales[Amount]),
TREATAS(VALUES(DisconnectedDate[Date]), Sales[Date])
)
To keep the Marketplace slicer populated, create a measure that lists all marketplaces with data in either date range. Example:
MarketplaceFilter =
VAR MarketsInRange1 =
CALCULATETABLE(
VALUES(Sales[Marketplace]),
TREATAS(VALUES(DisconnectedDate[Date]), Sales[Date])
)
VAR MarketsInRange2 =
CALCULATETABLE(
VALUES(Sales[Marketplace]),
TREATAS(VALUES(DisconnectedDate[Date]), Sales[Date])
)
RETURN
COUNTROWS(UNION(MarketsInRange1, MarketsInRange2))
Then, add your Sales[Marketplace] field to a slicer. In the slicer’s Visual-level filters, drag in MarketplaceFilter and set it to is not blank. This ensures the slicer shows all marketplaces from either date range, even if the ranges don’t overlap. Finally, use your measures in visuals like tables or charts to compare Sales_DateRange1 and Sales_DateRange2. If you want a combined view, create TotalSales. Example:
TotalSales = [Sales_DateRange1] + [Sales_DateRange2]
If this helped solve the issue, please consider marking it 'Accept as Solution' so others with similar queries may find it more easily. If not, please share the details, always happy to help.
Thank you.
Hi @Simomazzi The problem might be because the marketplace slicer relies on overlapping date ranges to display options. To fix this, use independent date filters with disconnected date tables or combine the date ranges in the model. You can also adjust the slicer logic to not directly depend on the date filters.
Hi, using independent date filters with disconnected date tables and using filter function i fix the issue. Thanks
Check out the November 2025 Power BI update to learn about new features.
Advance your Data & AI career with 50 days of live learning, contests, hands-on challenges, study groups & certifications and more!