Skip to main content
Solved

Flow of columns after using group Aggregator

  • November 7, 2022
  • 2 replies
  • 141 views

Forum|alt.badge.img

Hello All,

I am using group aggregator in our plan but I am not sure how to make all the columns flow from input till the end/output through group aggregator.

 

Best answer by alexAguilarMx

hi @Abby 

 

The group aggregator has two output endpoints. 

  • out_results endpoint contains the result of your group aggregator step
  • out sends the input records to subsequent steps.

You can use a join step after the group aggregator, it joins two separate data flows into a single data flow, this is the way to keep all columns 

 

 

View original
Did this topic help you find an answer to your question?

2 replies

alexAguilarMx
Data Pioneer
Forum|alt.badge.img+2
  • Data Pioneer
  • 9 replies
  • Answer
  • November 11, 2022

hi @Abby 

 

The group aggregator has two output endpoints. 

  • out_results endpoint contains the result of your group aggregator step
  • out sends the input records to subsequent steps.

You can use a join step after the group aggregator, it joins two separate data flows into a single data flow, this is the way to keep all columns 

 

 


Forum|alt.badge.img
  • Data Voyager
  • 16 replies
  • February 20, 2025

Hi ​@alexAguilarMx based on your suggestion, I applied the same to my use case but I found out that the left and the right join produces the same column names. For example, SUPPLY_CREATE_DATE that is created in one of the aggregate sets appear twice both on left and right after the join, so I have left.SUPPLY_CREATE_DATE and right.SUPPLY_CREATE_DATE. Ideally, after the join, I should take the right side for the aggregation since I would expect the column to come from the out_results only?

On a side not, I have several aggregator sets which each set has condition on the ‘when’ configuration. 


Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings