Hi how are you?? it is not a duplicate, because the "Active loc." has 3 values for that SKU, you probably have a join where the relationship is not 1 to 1 between SKU and "ACTIVE LOC.", which you should check, or SKU is not your key field.
if it comes straight from a table, without having to go through a join before (linking tables), it means that you will not have a unique SKU record, it is not key, now if you are interested in obtaining only one record for each SKU, you should think of a criterion, this you should analyze. Stop being duplicated when at least one value in some non-key field is different from the others, in your case "Active Loc." has 3 different values for an SKU.
I defiantly want to show duplicates regardless of the Avitve Loc. Maybe this is a stupid question, but could I load the same table twice to generate two tables to keep the SKU as its on entity? Would this then be able to filter because it would no longer be associated in the same table?
I am not so good at development myself, but I think maybe using the Peek() function to look at the next row value and checking if it matches the prior may be the way to go, and if you get a match, you load the record, otherwise you proceed to the next one. Unfortunately I cannot give you an example, maybe someone else can run with things from here potentially.
To help users find verified answers, please don't forget to mark a correct resolution or answer to your problem or question as correct.