Skip to Content
0
Oct 11, 2016 at 03:00 AM

Join node shows different results compared to underlying aggregation

113 Views Last edit Oct 11, 2016 at 12:00 AM 2 rev

Hi there

I am working on a requirement where the weights have to be created and rolled up based on counts of certain parameters - such as Goals, Objectives, Key initiatives, Activities and Responses.

A Goal can have multiple Objectives, an objective can have multiple Key initiatives and so on.

I started aggregating from the lowest level for the count for this, but while it works on the lowest level, the second level (from bottom) shows me weird results. I see good values in the aggregation level, but that's not what I see after the join.

Aggregation 2 and join 2 are the ones in question. The column I am concerned about, is COUNT_ACTIVITY

For Goal 1, Objective 1 and Key initiative 1, the count from Aggregation 2 returns 2, which is the expected value.

But when I join it back (join_2), I see different values for the same variable. Please see the screenshot below.

For Goal 1, Objective 1 and Key initiative 1, the count from Aggregation was 2, but from join, I get 4.

I was expecting to see 2 (from the aggregation) against all rows corresponding to Goal 1, Objective 1 and Key initiative 1.

Am I doing something wrong here? I haven't come across something like this earlier.

Thanks in advance!

Attachments

join-results.jpg (42.9 kB)