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

Data Days is here! Join us now for 60+ days of learning, challenges, and connection. Learn more

Reply
Anonymous
Not applicable

Lookupvalue between Start Date and End Date

I need to create a calculated column named Printer[Department], with a lookup formula from Employees table, considering start date and end date.

 

I tried this with no sucess:

Calculate(Values(Employees[Department]);
Filter ( Employees;
Printer[Date] >= Employees[Start Date] && Printer[Date] <= Employees[End Date] && Printer[Username] = Employees[Username]))

The relation is many to many, because at employees table a username(employee) can have one or more Department, regarding the period.

Example: the first username worked in 2 Departments.:

lookvalue.png

1 ACCEPTED SOLUTION
Stachu
Community Champion
Community Champion

this syntax should work:

Department =
VAR __RelevantEmployeeRows =
    FILTER (
        'Employees',
        'Employees'[Username] = 'Printer'[Username]
            && 'Employees'[Start Date] <= 'Printer'[Date]
            && 'Employees'[End Date] >= 'Printer'[Date]
    )
VAR __RelevantDepartments =
    DISTINCT (
        SELECTCOLUMNS ( __RelevantEmployeeRows, "Departments", 'Employees'[Department] )
    )
RETURN
    CONCATENATEX ( __RelevantDepartments, [Departments], "," )

the code assumes that there always is not null end date for each row in the Employees table

 

I'd also suggest to remove the many:many relationship in favour of a separate table with unique Usernames and 1:many, many2many relationships are not what most users think they are AND quite often if they have Both filtering direction are causing the relationship ambiguity - see detailed explanation here:
https://sqlbits.com/Sessions/Event18/Different_types_of_many-to-many_relationships_in_Power_BI



Did I answer your question? Mark my post as a solution!
Thank you for the kudos 🙂

View solution in original post

1 REPLY 1
Stachu
Community Champion
Community Champion

this syntax should work:

Department =
VAR __RelevantEmployeeRows =
    FILTER (
        'Employees',
        'Employees'[Username] = 'Printer'[Username]
            && 'Employees'[Start Date] <= 'Printer'[Date]
            && 'Employees'[End Date] >= 'Printer'[Date]
    )
VAR __RelevantDepartments =
    DISTINCT (
        SELECTCOLUMNS ( __RelevantEmployeeRows, "Departments", 'Employees'[Department] )
    )
RETURN
    CONCATENATEX ( __RelevantDepartments, [Departments], "," )

the code assumes that there always is not null end date for each row in the Employees table

 

I'd also suggest to remove the many:many relationship in favour of a separate table with unique Usernames and 1:many, many2many relationships are not what most users think they are AND quite often if they have Both filtering direction are causing the relationship ambiguity - see detailed explanation here:
https://sqlbits.com/Sessions/Event18/Different_types_of_many-to-many_relationships_in_Power_BI



Did I answer your question? Mark my post as a solution!
Thank you for the kudos 🙂

Helpful resources

Announcements
Fabric Data Days is here Carousel

Fabric Data Days 2026

Don't miss out on Data Days, June 15 through August 7. Learn Fabric, Power BI, SQL, AI and more.

May Power BI Update Carousel

Power BI Monthly Update - May 2026

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

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.