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
This strikes me as solving a problem that the architecture is meant to avoid, but I have two related tables. The first: SummaryInput, has unique rows of [Asset ID]. The second, AssetReturn, has a bunch of calculations, including periodic (monthly) cash flows, etc., so many more rows, but many fewer columns and is related via [Asset ID]. As shown in SUmmaryInput below, each asset has a yield associated with it. I'd like to think I wouldn't have to flatten that column of data from SummaryInput into AssetReturn to conduct weighted average calculations, but I haven't figured out another way yet.
So the question is what's the way to get the Yield into AssetReturn table?
SUMMARYINPUT:
| Number | Asset ID | Project | Yield |
| 1 | EC135 (MSN 0467) | Alpha | 18.42% |
| 2 | EC135 (MSN 0472) | Alpha | 18.42% |
| 3 | EC145 (MSN 9084) | Alpha | 18.15% |
| 4 | H4 (MSN 4) | Bravo | 17.00% |
| 5 | H5 (MSN 5) | Bravo | 17.00% |
| 6 | H6 (MSN 6) | Bravo | 17.00% |
| 7 | H7 (MSN 7) | Bravo | 17.00% |
| 8 | H8 (MSN 😎 | Bravo | 17.00% |
| 9 | H9 (MSN 9) | Bravo | 17.00% |
| 10 | H10 (MSN 10) | Bravo | 17.00% |
| 11 | H11 (MSN 11) | Bravo | 17.00% |
| 12 | H12 (MSN 12) | Bravo | 17.00% |
| 13 | H13 (MSN 13) | Bravo | 17.00% |
| 14 | H14 (MSN 14) | Bravo | 17.00% |
| 15 | H15 (MSN 15) | Charlie | 18.32% |
| 16 | H16 (MSN 16) | Delta | 18.34% |
| 17 | H17 (MSN 17) | Echo | 14.61% |
| 18 | H18 (MSN 18) | Echo | 20.74% |
| 19 | H19 (MSN 19) | Echo | 18.17% |
Summarized Table of ASSETRETURN
| Number | Asset ID | Calendar Month | Yield |
| 1 | EC135 (MSN 0467) | 3/31/2019 | 18.42% |
| 2 | EC135 (MSN 0467) | 4/1/2019 | 18.42% |
| 3 | EC135 (MSN 0467) | 5/1/2019 | 18.42% |
| 4 | EC135 (MSN 0467) | 6/1/2019 | 18.42% |
| 5 | EC135 (MSN 0467) | 7/1/2019 | 18.42% |
| 6 | EC135 (MSN 0467) | 8/1/2019 | 18.42% |
| 244 | H4 (MSN 4) | 12/1/2020 | 17.00% |
| 245 | H4 (MSN 4) | 1/1/2021 | 17.00% |
| 246 | H4 (MSN 4) | 2/1/2021 | 17.00% |
| 247 | H4 (MSN 4) | 3/1/2021 | 17.00% |
| 248 | H4 (MSN 4) | 4/1/2021 | 17.00% |
| 249 | H4 (MSN 4) | 5/1/2021 | 17.00% |
Solved! Go to Solution.
Hi,
In the Asset return Table, write this calculated column formula
=RELATED(SummaryInput[Yield])
Hope this helps.
Hi,
In the Asset return Table, write this calculated column formula
=RELATED(SummaryInput[Yield])
Hope this helps.
Thanks. My Excel tables had blanks in them so the [AssetID] that was linking was a "many-to-many" relationship that BI apparently didn't like at all. Once I removed the extra blanks from my Excel table, this worked perfectly.
Hi,
Glad to hear that. If my reply helped, please mark it as Answer.
The Power BI Data Visualization World Championships is back! Get ahead of the game and start preparing now!
| User | Count |
|---|---|
| 40 | |
| 37 | |
| 35 | |
| 34 | |
| 28 |
| User | Count |
|---|---|
| 136 | |
| 99 | |
| 73 | |
| 66 | |
| 65 |