
1. Re: One to many join duplicates rows, blending nullifies filtering, solution?
Robert Hyatt Jan 17, 2020 6:51 AM (in response to Robert Hyatt)Through more searching I finally found the answer! Thank you to Wim Kegels for the info he gave in a thread a few years back.
Basically the workaround is to do the join, let the dups remain, then create an LOD calculated field with a MIN function to only calculate 1 of the dup rows in your totals. I get this may not work for every situation, but it solved mine. Below are the steps Wim gave.
use Level of Detail calculations. In a fully joined data source (30 records), the following resulted in the correct number of hours / employee:
sum({ FIXED [Date], [Client]: MIN([Hours])}). This calculation looks per date and per client, then selects the minimum amount of hours (which is the same for all three entries for that client on that date) and takes the sum over the whole dataset.