March 31 - April 2, 2025, in Las Vegas, Nevada. Use code MSCUST for a $150 discount! Early bird discount ends December 31.
Register NowBe one of the first to start using Fabric Databases. View on-demand sessions with database experts and the Microsoft product team to learn just how easy it is to get started. Watch now
Hello,
i basically have one base table consisting of two columns: Date and ranking.
I now want to merge two other tables into this. Both tables contain the same column (working hours, cost centre) but i need to merge the one table with the base table based on the ranking of the day, the other table based on the weekday.
I can create a new column giving the weekday as output and then join the third table using that, but it will create a table with two cost centre columns in the same row.
However in the final result, all cost centres should be not in the same row so i can still get the total of working hours per cost centre and day.
View post on imgur.com
Hi @Bsngr ,
I don't think 'day of week' fields suitable to use as relationship column, it obviously will existed duplicate values so you can only get summary result when you use key column to get related records.
I'd like to suggest add a unique key column to help relationship mapping more accurate.
Regards,
Xiaoxin Sheng
March 31 - April 2, 2025, in Las Vegas, Nevada. Use code MSCUST for a $150 discount!
Arun Ulag shares exciting details about the Microsoft Fabric Conference 2025, which will be held in Las Vegas, NV.
User | Count |
---|---|
114 | |
76 | |
57 | |
52 | |
44 |
User | Count |
---|---|
164 | |
116 | |
63 | |
57 | |
50 |