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.
Rephrasing his idea as mine: The tool defaults the expressions to use [RowCount]. If you should either "Update Existing Field" or change the "Create New Field" the default expressions MUST be updated manually. Please update the expressions to make use of the new field.
Well, that doesn't always work! Often it will. But if you change the TYPE to date, it certainly won't. In fact, I see many questions about joining from within a DATE RANGE and the technique to build date rows from the range requires the use of DateTimeAdd(). Wouldn't it be nice (like your sample workflows) to modify the default expression based on the change of data type? I think so.
If we were thinking easy. Suppose you could have a RANGE function (dates or numerics) where you simply selected the from, to fields and gave the user the option to select the units. Now the tool auto-configures itself to create all of the "days" between the from and to dates or "1.0" and it creates all unit values between the two numeric amounts.
These would be "Alteryx" worthy enhancements in my opinion.