Find everything you need to get certified on Fabric—skills challenges, live sessions, exam prep, role guidance, and a 50 percent discount on exams.
Get startedEarn a 50% discount on the DP-600 certification exam by completing the Fabric 30 Days to Learn It challenge.
Have several tables that need Joining to a single 'master'. Assuming there are no steps between each join, what is the best practice?
Hi @jcountryman ,
Based on my test, you may use the second way to deal with your data and refer to blow issue:
Regards,
Daniel He
Thank you, but that doesn't quite address my question. Which is more efficient?
#"Step1" = Table.NestedJoin(MASTER,{"UID"},TABLE_1,{"UID"},"SUB_TABLE_1"), #"Step2" = Table.NestedJoin(#"Step1",{"UID"},TABLE_2,{"UID"},"SUB_TABLE_2"), #"Step3" = Table.NestedJoin(#"Step2",{"UID"},TABLE_3,{"UID"},"SUB_TABLE_3"), #"Step4" = Table.ExpandTableColumn(#"Step3","SUB_TABLE_1",{"Col2","Col3"}), #"Step5" = Table.ExpandTableColumn(#"Step4","SUB_TABLE_2",{"Col4","Col5"}), #"Step6" = Table.ExpandTableColumn(#"Step5","SUB_TABLE_3",{"Col6","Col7"})
#"Step1" = Table.ExpandTableColumn(
Table.NestedJoin(MASTER,{"UID"},TABLE_1,{"UID"},"SUB_TABLE_1"),
"SUB_TABLE_1",
{"Col2","Col3"}
), #"Step2" = Table.ExpandTableColumn(
Table.NestedJoin(#"Step1",{"UID"},TABLE_2,{"UID"},"SUB_TABLE_2"),
"SUB_TABLE_2",
{"Col4","Col5"}
), #"Step3" = Table.ExpandTableColumn(
Table.NestedJoin(#"Step2",{"UID"},TABLE_3,{"UID"},"SUB_TABLE_3"),
"SUB_TABLE_3",
{"Col6","Col7"}
)