My solution!
Now I'm off to do some pre-race stretching for next week. And polish my out-of-office email so no one bothers me starting at 9am PST on Monday. :)
At any rate... it works. Especially for factorials 17! and lower. :)
Cheers! NJ
My solution below
And used in the workflow below
I find it particularly difficult to keep all the input fields, keep the same input names and keep the same field order without a shed load of action tools. Any advice on this?
Attached!
EDIT: @NicoleJohnson I now see that our solutions are nearly identical :)
@PhilipMannering In regards to your action tools, I would make a couple tweaks to avoid this:
1) I would check the box on your macro input about show field map. This is a powerful option where whatever the field name that comes in from the workflow, it converts it to whatever field name is in the macro input. For this case, it would convert the fieldname "Number" to "vals".
2) I would add a select tool at the end, and then connect an action tool from the macro input to your select tool using the "update select with reverse field map" option. This is the way to change vals back to Number so that the user never knows that the fieldname was changed.
3) I would change your join tool so that your field is named vals instead of right_vals. For #2 to work, it has to find the field vals exactly to convert it back.
Now you can delete all the action tools and your interface as well:
Hope that helps!
Hi all I've returned after my lack of internet hiatus (plus moving to TheInformationLab) :)
I think I like the elegance of other people's solutions more but here was how I solved it
Nice one! I rarely use the Generate rows tool but it was very helpful in this case. :)
