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!Calling all Data Engineers! Fabric Data Engineer (Exam DP-700) live sessions are back! Starting October 16th. Sign up.
I'm helping our HR department with extracting employee information from our HR system via O-datafeeds.
This information comes in several tables with each a begin date and an end date per line.
The problem I'm currently have is related to slicers for determining reference dates. In the current situation I have to use two date slicers per table to determine the right reference date. When for example 3 tables are used, 6 slicers need to be filled in.
All tables are related. When I tried to use a autocallender table to filter all begin dates I can't make the relationship active for more than one table.
Is there any way I can make these date slicers more user friendly?
Thanks in advance.
@Boventje17 , I think you can create two date tables. Join one with all Begin dates and one join with all end dates. If there are from a different table. Nothing more has to be done. You can use slicer from tables.
If they are from the same table you can use userelation to change join. In such cases, you will have one active and other joins will be inactive.
refer this for userelation -https://community.powerbi.com/t5/Community-Blog/HR-Analytics-Active-Employee-Hire-and-Termination-tr...
Join the Fabric FabCon Global Hackathon—running virtually through Nov 3. Open to all skill levels. $10,000 in prizes!
Check out the September 2025 Power BI update to learn about new features.