I see.

So you are saying that it is just comparing the text of the case statement in the select clause with the text of the case statement in the group...

Right.

But we are changing the order of the select (or the Group By) not the when clause. And if you do - you get an error that says that #lab.Plans...

That would be the same as using a case statement but it leaves you with an empty (null) column.

I was trying to not have the column at all, if possible....

I was looking at the result as well and it looks good.

But I did notice that the order in the group by clause (case statement) has to be in exactly...

Actually the first set also gives duplicates (mode = 0).  It is the nulls that are duplicates.

I can fix it by using DISTINCT but not sure if that...

The union does give flexibility to how the rows are handled.

I did it like your first suggestion and just changed valueType to allow me to use the where...

That wasn't really what I meant but I figured out how to do it. 

I can't stop all three from being sent from the cross apply, but I...

Another question on the above cross apply.

Using the above Cross Apply where we have 3 rows coming back, is there a way to tell it to only send...

I do like that simplification.

Thanks.

That helped a lot.

Here is the solution that is a little closer to what I was trying to achieve

I have 2 tables (old values and new...

That's fine.
But I don't need a list of names (my mistake).  I need to use another value in the record to go along with the names in each record. ...

That could be.

But if I press the disable rule, I get an error and there is no close button.

I did get my query to work using this and I figured out how the calculation worked,

I was confused on the syntax of the 2nd Cross Apply:

It looks like it works. Just not sure why.

I understand what the cross applys are doing just not sure why a couple of things are for.

For...

Something like:

Thanks.