is guess the stamp transform is missing the ability to set the column name.
I want to do some date transformations like give me the first and last day of next month from now. I think I will need some stamp fields to do this. I would later reference those fields as variables to build the calculations/replaces, so different names from “stamp” would be pretty helpful
that’s right…
The naming of newly created columns is a bit unconsistent… sometimes you have a field with a autogenerated name you can edit, sometimes you have to tick a box first and sometimes you have to use a Rename Cols transform…
I like the the first way best: have a form field ready with an auto generated name…
Sometimes the column name is generated dynamically from the options chosen (such as Calculate). Sometimes it is fixed (such as Stamp). We use different approaches in each case.
Copy Cols is tricky, because it can create multiple copies of multiple columns. It could perhaps have an option to disambiguate them though. E.g. make 2 copies each of X and Y columns to go from columns:
Look at how different If vs Lookup and Calculate handle naming new cols. What’s the reason for that? And then there is Stamp, which needs a Rename.
Why can’t every transform, that creates a new col name it like if in the most easiest way? The content of the name could be filled automatically, until the user enters his title. And you could add a checkbox to go back to auto-naming, as long as the user does not enter anything in the name-field again…
Why should something like that not work out for every transform?
And why do you think the naming should work differently for If and Stamp?