Register now to learn Fabric in free live sessions led by the best Microsoft experts. From Apr 16 to May 9, in English and Spanish.
Hi,
I've scratched my head for several days now, trying to figure out this problem with RELATED and one-to-many relationship.
My relationship:
My measure:
Is Indeks salg a measure or calculated column?
If it's a measure then there's this issue:
You have the basic premise right in that RELATED will allow you to get a value from a dimension table (Booking Administration), but... you need to be iterating the fact table (Certus Bordereau) to do it. You need a row context from the fact table, then RELATED will follow the relationship from the fact (for the current row) to the dimension and get the single value for your column.
Right now, you're not iterating the fact anywhere in your measure.
Thanks for the quick response, both of you.
How can I supposed to iterate the fact table in this situation?
@amitchandak is mentioning making a column in the many table with the one tables value. I've tried that too and I can make a column in many (Certus Bordereau) with just:
column = RELATED('Booking Administration'[IndexDate])
But my understanding with using a date in a measure, then you need to have it wrapped by something like MAX, MIN, LASTDATE etc and I don't want that, since IndexDate is a unique value for each row in Booking Administration.
@psyclown , related work in one to many if you create a column on many sides from the one side Table.
On one side, you can try like this example
MAxx(RELATEDTABLE('Booking Administration'), [IndexDate])
refer if needed, 4 ways to copy data from one table to another
https://www.youtube.com/watch?v=Wu1mWxR23jU
https://www.youtube.com/watch?v=czNHt7UXIe8
Covering the world! 9:00-10:30 AM Sydney, 4:00-5:30 PM CET (Paris/Berlin), 7:00-8:30 PM Mexico City
Check out the April 2024 Power BI update to learn about new features.
User | Count |
---|---|
114 | |
99 | |
82 | |
70 | |
60 |
User | Count |
---|---|
149 | |
114 | |
107 | |
89 | |
67 |