Power BI is turning 10, and we’re marking the occasion with a special community challenge. Use your creativity to tell a story, uncover trends, or highlight something unexpected.
Get startedJoin us for an expert-led overview of the tools and concepts you'll need to become a Certified Power BI Data Analyst and pass exam PL-300. Register now.
I have this DAX Code: and it quadrupled my value, is there something wrong with double crossjoins?
Get Total Hours = SELECTCOLUMNS( FILTER( CROSSJOIN(table_c, FILTER( CROSSJOIN(table_a,table_b), table_a[employee_id] = table_b[employee_id] && table_a[start_date] >= table_b[date_effective_start] && table_a[start_date] <= table_b[date_effective_end] && table_a[start_date] >= table_b[date_production] ) ), table_a[str_buid_state_code] = table_c[str_buid_state_code] && table_a[start_date] >= table_c[date_effective_start] && table_a[start_date] <= table_c[date_effective_end] ), "Field Name 1", table_a[start_date], "Field Name 2", table_a[employee_id], "Field Name 3", table_b[supvsr_id], "Field Name 4", table_c[sys_description], "Field Name 5", table_a[duration], //this value Quadrupled "Field Name 6", table_c[flag_a], "Field Name 7", table_b[id_dept], "Field Name 8", table_b[id_role], "Field Name 1", table_b[flag_active_employee] )
Solved! Go to Solution.
There is nothing wrong with nested CROSS JOINs and they will work as intended.
I do recommend a slightly different technique for debugging.
I haven't changed any of your code, just broken out the tables so it's easier to see what is going on.
The final RETURN statement can be updated to be RETURN T1 or RETURN T2 etc so you can see how the data looks as you walk through the debugging.
So try this
Get Total Hours = Var T1 = FILTER( CROSSJOIN(table_a,table_b), table_a[employee_id] = table_b[employee_id] && table_a[start_date] >= table_b[date_effective_start] && table_a[start_date] <= table_b[date_effective_end] && table_a[start_date] >= table_b[date_production] ) ) Var T2 = FILTER( CROSSJOIN(table_c,T1 , table_a[str_buid_state_code] = table_c[str_buid_state_code] && table_a[start_date] >= table_c[date_effective_start] && table_a[start_date] <= table_c[date_effective_end] ) Var T3 = SELECTCOLUMNS(T2 , "Field Name 1", table_a[start_date], "Field Name 2", table_a[employee_id], "Field Name 3", table_b[supvsr_id], "Field Name 4", table_c[sys_description], "Field Name 5", table_a[duration], //this value Quadrupled "Field Name 6", table_c[flag_a], "Field Name 7", table_b[id_dept], "Field Name 8", table_b[id_role], "Field Name 1", table_b[flag_active_employee] ) Return T3
But I would probably create a SUMARIZE table of T2 which removes the duplicating durations.
There is nothing wrong with nested CROSS JOINs and they will work as intended.
I do recommend a slightly different technique for debugging.
I haven't changed any of your code, just broken out the tables so it's easier to see what is going on.
The final RETURN statement can be updated to be RETURN T1 or RETURN T2 etc so you can see how the data looks as you walk through the debugging.
So try this
Get Total Hours = Var T1 = FILTER( CROSSJOIN(table_a,table_b), table_a[employee_id] = table_b[employee_id] && table_a[start_date] >= table_b[date_effective_start] && table_a[start_date] <= table_b[date_effective_end] && table_a[start_date] >= table_b[date_production] ) ) Var T2 = FILTER( CROSSJOIN(table_c,T1 , table_a[str_buid_state_code] = table_c[str_buid_state_code] && table_a[start_date] >= table_c[date_effective_start] && table_a[start_date] <= table_c[date_effective_end] ) Var T3 = SELECTCOLUMNS(T2 , "Field Name 1", table_a[start_date], "Field Name 2", table_a[employee_id], "Field Name 3", table_b[supvsr_id], "Field Name 4", table_c[sys_description], "Field Name 5", table_a[duration], //this value Quadrupled "Field Name 6", table_c[flag_a], "Field Name 7", table_b[id_dept], "Field Name 8", table_b[id_role], "Field Name 1", table_b[flag_active_employee] ) Return T3
But I would probably create a SUMARIZE table of T2 which removes the duplicating durations.
This is your chance to engage directly with the engineering team behind Fabric and Power BI. Share your experiences and shape the future.
Check out the June 2025 Power BI update to learn about new features.
User | Count |
---|---|
57 | |
55 | |
55 | |
37 | |
30 |
User | Count |
---|---|
79 | |
66 | |
45 | |
44 | |
42 |