Introduction

Enriching data is at the heart of analysis modelling from adding additional data and extrapolating information to performing complex calculations and deduplication, PhixFlow covers it all. In this page we will highlight some of the key areas of enrichment, provide examples, and list the links to additional useful enrichment resources.

PhixScript Functions

PhixScript is the language of PhixFlow and it can be used anywhere that supports expressions, such as attributes on a table and in filters.

There are over 115 functions available and these are listed in Functions. but to help you get started here is a short list of commonly used functions:

Common Functions

1. Comments can be added to a single line using // or to a section using /* */.
2. if: used where you need to evaluate a simple condition before processing an expression.
3. ifNull: If its first value is provided then this is the returned value, else it will return the second value.
4. switch: evaluates a set of conditions in turn, and returns the associated result for the first match.
5. forEach: Iterates over an Array or Recordset and processes a script for each entry.
6. listToString: takes a list and returns a string delimited by a comma.
7. contains: Used on a string will return true (1), if a string contains another specified string.
8. listContains: Used on a list returns the position of a entry in a list (with 1 being the first item) if the value being looked for is found in the list, and false (0) otherwise.
9. replaceAll: Replace all occurrences of a pattern with a replacement string. Also see replaceFirst.
10. dateDiff: Return the time difference between two dates in milliseconds.
11. dateAdd: Add or subtract from a date using a specified unit e.g. _MONTH.
12. now: Returns the current day and time, and today returns just the day.
13. _NULL: is how to declare a null value e.g. $output = _NULL.
14. substring: Returns the portion of the supplied string between specified character positions.
15. stringLength: Returns the length of a string.
16. trim: Removes leading and trailing white spaces from a string, returning the cleansed string.
17. toString: Converts a value from select data types into a string. For example, a date.
18. toDate: Converts a string in a recognised date format (e.g. 20120521 or 20120521.172108) into a date.

Debugging

• debug: Adds a debug message into the Log. This function is often used when creating a model and trying to work out why an Expression is not behaving as expected.
• error: Adds a error message into the Log and displays the message to the user. 

Writing PhixScript

Where a PhixScript is more than a single function, it must be wrapped in a do() function. do() can also be used within functions where you need to carryout multiple functions such as in if or switch.

Single Function PhixScript

This is used in attribute expressions and filters alike where a single function is called.

// If ExamResult is greater than 95 then return "Distinction" else return "Pass"
if( in.ExamResult > 95, "Distinction", "Pass")

Multiple Function PhixScript

PhixScripts containing multiple functions must be wrapped in a do(). For more information see do().

The value returned from the PhixScript is the final value output, therefore it is useful to add the desired output to the end of the script.

Note that variables declared in an attribute expression (variables are declared with a $ symbol with the data type being implied) will be accessible to subsequent attributes within the same table by using the $variable name.

do(
	// calculate the miles per gallon.
	$mpg = in.distance / in.gallonsUsed,
	
	// if $mpg is over 65 set efficiency to Highly Efficient
	if( $mpg > 65, $efficiency = "Highly Efficient",
	
		// ELSE, set $efficiency to be null
		$efficiency = _NULL
	),	

	// Set the value returned by the PhixScript
	$efficiency
)

Variables

PhixFlow contains a number of Internal Variables available to PhixScript used for obtaining system and user information.

Variables in PhixFlow are declared using a $ variable. The data type is implied by the first value entered, for example:

1. $myArray  = []. Creates an array.
2. $myString = "Hello World". Create a string.
3. $myDate   = toDate("20120521"). Create a date.
4. $myNumber = 42. Create a number

Lookup Information

Lookups can be performed using three different techniques, the method selected depends on your requirements and these are described below:

Lookup Function

See lookup for full details on the configuration.

The lookup function allows the user to pass variables to a lookup pipe. For example up, the pipe configuration for passing a variable would look like the following with the Type set to Lookup:

To retrieve the Region data from this lookup pipe, for example in an attribute expression, this would look like the following: lookup(in, $num = _out.MyValue).Region

Lookup with Filtering

Scenario

Lookup information from a separate table and pass filtering information to return only selected records. 

Example

You need to retrieve the region for a particular businesses. We will use the City to perform a lookup that will return a region.Solution

1. You should have a two tables:
   1. one with your data that will perform the lookup e.g. Business Data.
   2. a second table with the data being looked up e.g. Region.
2. Drag a pipe from the data to be looked up, to the data performing the lookup. In our case from Region to the Business Data.
3. In the properties window that opens for the pipe:
   1. Set the name to be something short but meaningful.
   2. Set the Type to be lookup.
   3. In the filter section we will tell the lookup pipe we want to filter Region by City using the processed City value from our Business Data.
   4. We are passing data and not just a string value, so click to tell PhixFlow we are passing an expression.
      1. To use the processed version of City we use _out.City.
      2. The filter as follows:
      3. 
4. The lookup is now setup, to access the Lookup attributes, we open the Business Data and add an attribute called Region.
   1. In the expression type pipe.attribute, in our case this will be rgn.Region.
   2. Save your changes.
5. Run analysis on Business Data and the Region will now populate.

Lookup with Order/Index

Scenario

This is a highly efficient method for performing a lookup against a small set of records. This kind of lookup will automatically cache a set amount of records, 3000 by default, in memory allowing for faster lookups.

Example

You have a product ID on an invoice and want to return the name of the product to display. There are a finite amount of products so it is efficient to cache them.

Solution

Merges

See Merging Tables.

Matching

Simple exact matches and make reference to addition al functions for more advanced matching see Lev Distance etc.

Task Plan

For full details see Using Tasks and Task Plans. 

Task plans can be used to run analysis from an action or at a schedule time(s). There are additional features which enable you to clear data and perform system tasks. To setup a Task Plan which:

• Runs every day at 1am.
• Runs the Analysis Task 1, before Analysis Task 2.

Example Solution

1. Create a new Task Plan in your application from within the repository.
2. Tick Enabled and Scheduled.
3. Click  Apply
4. Add your tasks, click the ellipses → Add New Item → Select your item.
5. Complete the details and tick Mandatory if you want this task to complete before moving onto the next task in your task plan.
6. Save your task, and add any additional tasks. Your Task plan will look similar to this: 
   1. 
7. In the Schedule, complete the details as required, in our example we have set the Task Plan to run everyday at 1am. Note: * means all values, and ? means no value. You will find more information on this in the Task Plan help pages mentioned above.
   1.