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.
I'd create a metadata input that includes a SORT_ORDER field for column A. Home = 0, First = 1 etcetera. Using a Find Replace tool, I'd add that field to the initial table and sort on the new SORT_ORDER field. Once the field is used, you can de-Select it.
Alteryx ACE & Top Community Contributor
Chaos reigns within. Repent, reflect and reboot. Order shall return.
Just wanted to confirm with you that the following is the logic behind the workflow:
- You have programmed the workflow such that the input list is effectively joining for the second column's record in the first column using the sample tool to skip the first row and attaching it back into the list to find itself...
- The iterative macro is required because you are effectively using the 2nd columns first row to do a vlookup (in excel land) of itself in the first column which will then loop the "remaining" records to find itself again...
Just wondering how I can explain the logic behind this to others...keen to hear your thoughts & explanation.