Hi Jeroen, happy friday! I feel like the AttributeValueMapper could be the solution to your question, but this requires some hard coding of values. A dynamic way of solving this, is using the AttributeExploder:

This is my starting data: 

First you explode your Applicant table using the AttributeExploder (Keep Attributes = Yes), then you use the FeatureMerger to merge the Score values to your attributes (Requestor = _attr_name, Supplier = Certification). You now have the Score field added to your exploded Applicant table:

Using a Tester we filter out the features where the Certification Type mentioned in _attr_name  is not equal to “url”, In your case you might have to resort to using “Attribute Has A Value”. You have to make sure you refer to @Value(@Value(_attr_name)), as you want the value of the certification type mentioned in Certification:

This leaves us with 4 features for 3 applicants, one feature for every certification every applicant has.

Using an AttributeCreator we can map our Score value in our Certification_X columns:

Using an Aggregator we recreate our old Applicant table, making sure to Group on Applicant_ID and create a list of scores:

Using a ListSorter, we sort our list Descending. If an applicant has multiple scores, the highest one will be the first list entry. We then use a final AttributeCreator to create an attribute Highest_score:

And there we have the highest score per Applicant_ID.

I hope this helps. I also cannot wait for some Evangelists to recreate my outcome using only 2,5 transformers ;-) 

Have a great weekend!

Hi Jeroen, happy friday! I feel like the AttributeValueMapper could be the solution to your question, but this requires some hard coding of values. A dynamic way of solving this, is using the AttributeExploder:

This is my starting data: 

First you explode your Applicant table using the AttributeExploder (Keep Attributes = Yes), then you use the FeatureMerger to merge the Score values to your attributes (Requestor = _attr_name, Supplier = Certification). You now have the Score field added to your exploded Applicant table:

 

Using a Tester we filter out the features where the Certification Type mentioned in _attr_name  is not equal to “url”, In your case you might have to resort to using “Attribute Has A Value”. You have to make sure you refer to @Value(@Value(_attr_name)), as you want the value of the certification type mentioned in Certification:

This leaves us with 4 features for 3 applicants, one feature for every certification every applicant has.

Using an AttributeCreator we can map our Score value in our Certification_X columns:

Using an Aggregator we recreate our old Applicant table, making sure to Group on Applicant_ID and create a list of scores:

Using a ListSorter, we sort our list Descending. If an applicant has multiple scores, the highest one will be the first list entry. We then use a final AttributeCreator to create an attribute Highest_score:

And there we have the highest score per Applicant_ID.

I hope this helps. I also cannot wait for some Evangelists to recreate my outcome using only 2,5 transformers ;-) 

Have a great weekend!

Great solution.

@joepk Sorry for the late reply.

Thank you very much for the detailed answer. This was the solution for me!