This site uses different types of cookies, including analytics and functional cookies (its own and from other sites). To change your cookie settings or find out more, click here. If you continue browsing our website, you accept these cookies.
Find answers, ask questions, and share expertise about Alteryx Designer.
General Discussions has some can't miss conversations going on right now! From conversations about automation to sharing your favorite Alteryx memes, there's something for everyone. Make it part of your community routine!
It took me some time to understand what is the goal of the exercise and I think @Qiu created elegant solution for you. I have a quick question as I am curious about it why do you need a data in this format?
Hi @Qiu , Thanks for your solution, really appreciate your effort to help me out with this!
Just a quick question - it seems that the Unique Tool is not quite the right tool to use as it is deleting the duplicates even though they are actually not duplicates. For example: Teacher has 2 different 'Year Joined' but contain same age. One of the age is deleted by Unique Tool. I am having this problem hence not I am looking for other solution.
[Unique Tool] [Intended Result]
@Emil_Kos - The list will be used as an input source to generate Tree UI using the Tree Interface Tool. I already have a workflow to assign reference key, all I need is to solve this puzzle.. Kudos to @Qiu !
I have marked your piece as the solution - one quick question though, may I know why you decided to split the 'Butcher' out and rejoin it at later stage? I cannot seem to understand how it would make difference.. Would you kindly enlighten me?