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!The Power BI Data Visualization World Championships is back! Get ahead of the game and start preparing now! Learn more
Hi, I have this calculated column in report view:
Solved! Go to Solution.
@Justas4478 Hi! If you don't want to merge, you can look up values from the second table dynamically, something like:
Table.AddColumn(#"Previous Step", "Calculated Column", each
Value.Divide(
[Absolute Difference Quantity],
List.First(
Table.SelectRows(
#"Product information",
each [Product ID] = _[Product ID]
)[Pick to Base UoM Quantity],
null
)
)
)
If performance is a concern and you want a cleaner approach, merging tables is the best way to go. If merging is not an option due to constraints, then the Table.SelectRows method can work but will be slower for large datasets.
BBF
@Justas4478 Hi! If you don't want to merge, you can look up values from the second table dynamically, something like:
Table.AddColumn(#"Previous Step", "Calculated Column", each
Value.Divide(
[Absolute Difference Quantity],
List.First(
Table.SelectRows(
#"Product information",
each [Product ID] = _[Product ID]
)[Pick to Base UoM Quantity],
null
)
)
)
If performance is a concern and you want a cleaner approach, merging tables is the best way to go. If merging is not an option due to constraints, then the Table.SelectRows method can work but will be slower for large datasets.
BBF
@BeaBF The performance concerns is my primary worry so I will try the merge in hopes that it is better over long term.
Thanks for the solution I know I will find where to use it.
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!
| User | Count |
|---|---|
| 10 | |
| 6 | |
| 5 | |
| 4 | |
| 2 |