Check your eligibility for this 50% exam voucher offer and join us for free live learning sessions to get prepared for Exam DP-700.
Get StartedDon't miss out! 2025 Microsoft Fabric Community Conference, March 31 - April 2, Las Vegas, Nevada. Use code MSCUST for a $150 discount. Prices go up February 11th. Register now.
Hi,
I need some help to understand how I should work with two fact tables that does not have all the dimensions in each fact table.
I have uploaded an example pbix so you can easily try it out.
Link to pbix:
I want to calculate the total salery amount based on days worked and the daily salery.
The model should also allow me to filter by location, salery type and month.
The issue I meet is that I don't have the location in the days worked table. I only know how many days they have worked. So when create a table it will not filter out Lisa who has not worked at Building 1. What is the best way of solving this?
Is it possible to create a measure that allows me to calculate the totalt salery correctly or maybe create one fact table with the days worked, and still be able to filter by location and salery type?
the wanted output in the example shold be:
Namedaily salerydays workedSallery total
Christian | 1700,95 | 23 | 39121,85 |
Scot | 1882,45 | 27 | 50826,15 |
Total | 3583,4 | 50 | 179170 |
Solved! Go to Solution.
In additions I implemented the solution for you. Below the calculated table (first disconnect Days and then calculate table!)
extraTable =
VAR __cartesian = ALL(Salery[EMP Number],Salery[Month], Salery[Location])
VAR __tableWithAllocatedDays =
ADDCOLUMNS(
__cartesian,
"@AllocatedDays",
DIVIDE(
SUMX(FILTER(Salery, Salery[EMP Number] = EARLIER(Salery[EMP Number]) && Salery[Month] = EARLIER(Salery[Month]) && Salery[Location] = EARLIER(Salery[Location])), Salery[Daily salery]),
SUMX(FILTER(Salery, Salery[EMP Number] = EARLIER(Salery[EMP Number]) && Salery[Month] = EARLIER(Salery[Month])), Salery[Daily salery])
) *
SUMX(FILTER('Days at work', 'Days at work'[Emp Number] = EARLIER(Salery[EMP Number]) && 'Days at work'[Month] = EARLIER(Salery[Month])),'Days at work'[Days])
)
RETURN
__tableWithAllocatedDays
Giving this visual:
Allocate the Days to a location on basis of the weighted average of Daily Salary per Location. So EMP number 1 will have the Days allocated for 99.9% to location 1 and for 0.1% to location 2.
Make a new table with these allocations, disconnect the old Days table and connect the new one to the dimension tables (including Locations).
Good luck!
In additions I implemented the solution for you. Below the calculated table (first disconnect Days and then calculate table!)
extraTable =
VAR __cartesian = ALL(Salery[EMP Number],Salery[Month], Salery[Location])
VAR __tableWithAllocatedDays =
ADDCOLUMNS(
__cartesian,
"@AllocatedDays",
DIVIDE(
SUMX(FILTER(Salery, Salery[EMP Number] = EARLIER(Salery[EMP Number]) && Salery[Month] = EARLIER(Salery[Month]) && Salery[Location] = EARLIER(Salery[Location])), Salery[Daily salery]),
SUMX(FILTER(Salery, Salery[EMP Number] = EARLIER(Salery[EMP Number]) && Salery[Month] = EARLIER(Salery[Month])), Salery[Daily salery])
) *
SUMX(FILTER('Days at work', 'Days at work'[Emp Number] = EARLIER(Salery[EMP Number]) && 'Days at work'[Month] = EARLIER(Salery[Month])),'Days at work'[Days])
)
RETURN
__tableWithAllocatedDays
Giving this visual:
Thanks you so much! You saved my week and I learned alot 🤩
March 31 - April 2, 2025, in Las Vegas, Nevada. Use code MSCUST for a $150 discount! Prices go up Feb. 11th.
Check out the January 2025 Power BI update to learn about new features in Reporting, Modeling, and Data Connectivity.
User | Count |
---|---|
18 | |
15 | |
14 | |
11 | |
8 |
User | Count |
---|---|
24 | |
19 | |
12 | |
11 | |
10 |