Set Transform

Literal example:

set col: Country value: 'USA'

Output: Sets the values of all rows in the Country column to USA.

Multi-column Literal example:

set col: SSN,Phone value: '##REDACTED###'

Output: Sets the values of all rows in the SSN and Phone columns to ##REDACTED##.

Expression example:

set col: isAmerica value: IF(Country == 'USA', true', 'false')

Output: If the value in the Country column is USA, then the value in isAmerica is set to true.

Placeholder example:

You can substitute a placeholder value for the column name, which is useful if you are applying the same function across multiple columns. For example:

set col:score1,score2 value:IF ($col == 0, AVERAGE($col), $col)

Output: In the above transform, the values in score1 and score2 are set to the average of the column value when the value in the column is 0. Note that the computation of average is applied across all rows in the column, instead of just the filtered rows.

Window function example:

You can use window functions in your set transforms:

set col: avgSales value: ROLLINGAVERAGE(POS_Sales, 7, 0) group: saleDate order: saleDate

Output: Calculate the value in the column of avgSales to be the rolling average of the POS_Sales values for the preceding seven days, grouped and ordered by the saleDate column. For more information, see Window Functions.

set col:col1,[col2] value:(expression) [group: group_col]

For more information on syntax standards, see Language Documentation Syntax Notes.

Identifies the column and optional additional columns to which to apply the transform.

set col: MyCol value: 'myNewString'

Output: Sets value in MyCol column to myNewString.

Usage Notes:

Identifies the expression that is applied by the transform. The value parameter can be one of the following types:

The expected type of value expression is determined by the transform type. Each type of expression can contain combinations of the following:

The types of any generated values are re-inferred by the platform.

Usage Notes:

Identifies the column by which the dataset is grouped for purposes of applying the transform.

If the value parameter contains aggregate or window functions, you can apply the group parameter to specify subsets of records across which the value computation is applied.

You can specify one or more columns by which to group using comma-separated column references.

Usage Notes:

This example illustrates the different uses of the replacement transformations to replace or extract cell data.

Source:

The following dataset contains contact information that has been gathered by your marketing platform from actions taken by visitors on your website. You must clean up this data and prepare it for use in an analytics platform.

Transformation:

Title column: For example, you first notice that some data is missing. Your analytics platform recognizes the string value, "#MISSING#" as an indicator of a missing value. So, you click the missing values bar in the Title column. Then, you select the Replace suggestion card. Note that the default replacement is a null value, so you click Edit and update it:

Title

if(ismissing([Title]),'#MISSING#',Title)

Request column: In the Request column, you notice that the reg entry should be cleaned up. Add the following transformation, which replaces that value:

Request

`{start}reg{end}`

Registration

The above transformation uses a Wrangle as the expression of the on: parameter. This expression indicates to match from the start of the cell value, the string literal reg, and then the end of the cell value, which matches on complete cell values of reg only.

This transformation works great on the sample, but what happens if the value is Reg with a capital R? That value might not be replaced. To improve the transformation, you can modify the transformation with the following Wrangle in the on parameter, which captures differences in capitalization:

Request

`{start}{[R|r]}eg{end}`

'Registration'

Add the above transformation to your recipe. Then, it occurs to you that all of the values in the Request column should be capitalized in title or proper case:

Request

proper(Request)

Now, all values are capitalized as titles.

Phone column: You might have noticed some issues with the values in the Phone column. In the United States, the prefix 555 is only used for gathering information; these are invalid phone numbers.

In the data grid, you select the first instance of 555 in the column. However, it selects all instances of that pattern, including ones that you don't want to modify. In this case, continue your selection by selecting the similar instance of 555 in the other row. In the suggestion cards, you click the Replace Text or Pattern transformation.

Notice, however, that the default Replace Text or Pattern transformation has also highlighted the second 555 pattern in one instance, which could be a problem in other phone numbers not displayed in the sample. You must modify the selection pattern for this transformation. In the on: parameter below, the Wrangle has been modified to match only the instances of 555 that appear in the second segment in the phone number format:

Phone

`{start}%{3}-555-%*{end}`

'#INVALID#'

true

Note the wildcard construct has been added (%*). While it might be possible to add a pattern that matches on the last four characters exactly (%{4}), that matching pattern would not capture the possibility of a phone number having an extension at the end of it. The above expression does.

LeadId column: You might have noticed that the lead identifier column (LeadId) contains some embedded information: a date value and an identifier for the instance within the day. The following steps can be used to break out this information. The first one creates a separate working column with this information, which allows us to preserve the original, unmodified column:

Single row formula

LeadId

'LeadIdworking'

You can now work off of this column to create your new ones. First, you can use the following replace transformation to remove the leading two characters, which are not required for the new columns:

LeadIdworking

'LE'

''

Notice that the date information is now neatly contained in the first characters of the working column. Use the following to extract these values to a new column:

LeadIdworking

Custom text or pattern

`{start}%{6}`

The new LeadIdworking2 column now contains only the date information. Cleaning up this column requires reformatting the data, retyping it as a Datetime type, and then applying the dateformat function to format it to your satisfaction. These steps are left as a separate exercise.

For now, let's just rename the column:

Manual rename

LeadIdworking1

'LeadIdDate'

In the first working column, you can now remove the date information using the following:

LeadIdworking

`{start}%{6}`

''

You can rename this column to indicate it is a daily identifier:

Manual rename

LeadIdworking

'LeadIdDaily'

Results:

This example illustrates how to use the conditional calculation functions.

Functions:

Source:

Here is some example weather data:

Transformation:

The following computes average temperature for rainy days by city:

Single row formula

AVERAGEIF(temp, rain > 0)

city

'avgTempWRain'

The following computes maximum wind for sub-zero days by city:

Single row formula

MAXIF(wind,temp < 0)

city

'maxWindSubZero'

This step calculates the minimum temp when the wind is less than 5 mph by city:

Single row formula

MINIF(temp,wind<5)

city

'minTempWind5'

This step computes the variance in temperature for rainy days by city:

Single row formula

VARIF(temp,rain >0)

city

'varTempWRain'

The following computes the standard deviation in rainfall for Center Town:

Single row formula

STDEVIF(rain,city=='Center Town')

city

'stDevRainCT'

You can use the following transforms to format the generated output. Note the $col placeholder value for the multi-column transforms:

stDevRainCenterTown,maxWindSubZero

numformat($col,'##.##')

Since the following rely on data that has only one significant digit, you should format them differently:

varTempWRain,avgTempWRain,minTempWind5

numformat($col,'##.#')

Results: