Want to get involved? We're always looking for ideas and content for Weekly Challenges.
SUBMIT YOUR IDEAMy Solution. Great Challenge.
#Spoiler
Nice challenge and fascinating seeing how others got to the answer!
Here is my attempt.
As with many of these challenges - they start out so deceptively simple, but then there is usually a catch! ;)
I left my original solution as-is, which means the now-infamous item #1119 got classified as "Outerwear" instead of "Jackets" as in the solution file.
I did an extra little investigation with the published solution workflow (hence the extra Output tool for the original data) to at least see what caused the difference! It looks like the "Unique" tool in the solution file took the first Field_1 entry, and that picked up the existing class for that record in the subsequent join in the solution. Sorry for babbling but that was a fun little educational quirk to see regarding the Unique tool!
not sure, if keeping fields in Aggregation via "First" or "Min" etc. is a good idea 😅