Overview

tables are a key model component. They represent a structured store of data within PhixFlow receiving data from one or more components, processing it then storing it.

For information about the properties toolbar, and about the sections Parent Details, Analysis Models, Description and Audit Summary, see Common Properties. We recommend you always add a Description that explains the purpose of the item you are creating.

For a full list of all the PhixFlow property tabs and windows, see Properties, Windows, Menus and Toolbars.

The tab toolbar has the following additional buttons:

Error rendering macro 'excerpt-include' : No link could be created for '_record_sets_show'.

,

Show view,

Run Analysis.

When you make changes to tables and attributes, PhixFlow automatically publishes them to the database; see Publishing Streams.

Property Pane Toolbar

For information about the toolbar options, see the Common Properties page, Toolbars and Controls section.

Properties Tab

Parent Details

If this item is within or belongs to another, its parent name is shown here. See the Parent Details section on the Common Properties page for more details.

Table Properties

Basic Settings

Field	Description
Name	The name of the table.
Model Validation Status	When you save changes to the properties of a table or view attribute, PhixFlow validates that the properties are set correctly. If there is an issue with the properties, PhixFlow indicates the status of the validation check: UNKNOWN - PhixFlow has not run the validation check yet. Save the properties to run the check. SUCCESS - the properties are set correctly ERROR - PhixFlow has found issues that need attention. Scroll down the properties to the Errors section where you will find the list of properties that need correcting. When a table or view attribute has validation errors, PhixFlow also reports that the parent application and package have errors. PhixFlow can process data from tables or view attributes that have validation errors. The validation checks help you to configure tables and view attributes so that PhixFlow can continue to run efficiently. For example, PhixFlow reports an error if a table has no Data Retention option set because it can affect performance when all old tablesets are retained, To run validation checks on all tables, view attributes, applications and packages, use Administration Menu → More → Validate Model Objects.
Enabled	Tick to include the steam during analysis runs.
Static Data	Tick to set the table to hold static data. Static data is reference or "look up" data that is used as part of a table calculation. Updating a static table In general, static tables are not updated during an analysis run that is initiated on another table in the model. The exception is when an incoming push pipe is triggered, as this will force the table to update itself. Instead, to update the data in a static table you must run analysis directly on the table via: the model a task plan.
Period	Select the time period for the table: Transactional: allows multiple users to run independent analysis tasks at the same time. Non-transactional Daily: generate or collect data every day. Monthly: generate or collect data every month. Variable: generate or collect data since the more recent run of the table to the current date. As transactional tables need a `UID` attribute, PhixFlow automatically creates this attribute if it does not already exist.
Default Data Range	This option affects the following items for which this is the backing table: views screens card components. Select which recordset data is displayed. Latest: displays the records from the latest recordset only. Recommended when recordsets are updated by batch process, and therefore have a Period of Daily or Monthly. All: displays the records from all recordsets. Recommended when recordsets are updated incrementally and therefore have a Period of Transactional or Variable. If no option is is selected, PhixFlow assumes the default data range is All. You can override this setting using the options Use Custom Data Range and Data Range available: on a Screen. on a card; see Component. You cannot override this setting for a view.
Table Type	Select the table type; see Types of Table. The type indicates the function that operates on the data. Aggregate Table Calculate Table CalculateBySet Table Cartesian Table Merge Table
Supersede Items on Pipe	Select a loop pipe from the list of those available. A loop pipe links the table back to itself. It compares new data records to the existing data records. If there is a repeated record PhixFlow uses the new one in the table and marks the old one as `superseded`.
Audit Manual Changes	This check box is available when the Period is Transactional. Tick to update and delete initiated by actions (not those carried out by analysis runs) will automatically mark the existing record as superseded and create a new recordset. The new versions of the updated records will be placed in the new recordset. Inserts will simply create a new recordset, and add the inserted record into that recordset. When Audit Manual Changes is first set, the attributes `UpdateAction`, `UpdatedByName`, `UpdatedByID` and `UpdatedTime` will be created if they do not already exist. If you do not require these attributes, delete them. For the `UpdatedByName` attribute, PhixFlow creates a field of 250 characters. (In versions up to 8.0.4, the field was 50 characters long.) `UpdateAction` must be set to the type of action, such as INSERT, UPDATE or DELETE. The other attributes will be populated if they exist on the table: `UpdatedByName` - the name of the user that performed the update, `UpdatedByID` - the internal id of the user that performed the update `UpdatedTime` - the date and time the update was made

Attributes

The grid contains a list of the attributes in the table. This section has a toolbar with standard buttons and Show Table and Show File Collectors.

The grid lists the attributes (data columns) in the table data. To edit the properties of an attribute, double-click the attribute name to open the Attribute properties.

To remove an attribute from the table, select the attribute and click Delete in the toolbar.

To add a new attribute to the list, click Create New to open a new Attribute properties tab.

To add an existing attribute to the list:

Click Show Table to list the tables available in the repository.
Expand a table to show its attributes.
Drag an attribute into this list to add it.

To edit only the expression:

Right-click an attribute name to display the context menu.
Select Edit the expression field.
PhixFlow opens a simple text editor box
Make changes to the attributes expression.
Click to save your changes.

Multipliers and Filters

Field	Description
Input Multiplier	The input multiplier expression should evaluate to a list of one or more values. For each value in the list, the internal variable _inputMultiplier will be set to that value and the whole table processing will be repeated i.e. the pull pipes will be read and the data from those pipes processed to generate output records to be added to the current recordset. For example : do ( $aRange = [], addElement($aRange, rng.RangeFrom), addElement($aRange, rng.RangeTo), $bRange = [], addElement($bRange, $aRange), $bRange ) Where rng.RangeFrom = 500 and rng.RangeTo = 1000, the above example evaluates to [[500,1000]], which is a list containing 1 element, which is itself a list containing 2 elements. An input multiplier that evaluates to [3,4,7,8] would run the Table 4 times. Because Input Multipliers are evaluated first in the PhixFlow Timing Cycle they are often used to look up values that can be passed to Database or other Collectors.
Log Input Multiplier Messages	Tick to cause PhixFlow to write a message to the log every time an Input Multiplier value changes during an analysis run.
Output Multiplier	This field is an expression which should evaluate to an array of values. A separate output record will be produced for each value in the array and this value is available as _outputMultiplier in each of the table output attribute expressions (each value in the array is also available through _type, although this is not recommended usage). In effect this will multiply each of the output records by the number of elements from the returned list. For example : ifNull(in.ASSET, [1,10,12] , // else do [5,7] ) will create 3 records for every record in the table if in.ASSET contains a value (setting _type = 1, 10 and 12 in each case). Otherwise it will create 2 records for every record in the table (and set _type = 5 and 7). An output multiplier may also evaluate to a record, or a group of records. For example an Output Multiplier with the expression: do( lookup(lkin, $num = in.BNumber), lkin ) will return a list of records which match the lookup on the lkin pipe. In this case the required data can be extracted from the Output Multiplier using the following expression : do ( $values = _type, $values.account_num ) If the output multiplier expression evaluates to _NULL, an empty list of values or an empty list of records then a single output record will be produced with _type set to _NULL, _NULL or an empty record respectively.
Select Records to Output	You can select a subset of records to output to the next modelling object. You select records using the data in any attribute that is in the table output. Enter an expression that should evaluate to true or false (equivalently 1 or 0). When the expression evaluates to true or 1, the records found by the expression are selected and output to the next modelling object. For example: A table containing data about accounts has an attribute called "active". You only want to include "active" accounts in the following tables. Active accounts have the value 1. To select active accounts, enter the expression `_out.active`. All records that have the active attribute set to any other value are ignored.

Actions

This section has a toolbar with standard buttons. The grid contains a list of actions that operate on the table.

To edit the properties of an action, double-click its name. To add an action to the list, click Create New. PhixFlow opens the Action properties tab.

To remove an action from the table, select the action and click Delete in the toolbar.

Record-Actions

This section has a toolbar with standard buttons. The grid contains a list of record-actions that can update records in the table.

To edit the properties of a record-action, double-click its name. To add a record-action to the list, click Create New. PhixFlow opens the Record-Action properties tab.

To remove a record-action from the table, select the record-action and click Delete in the toolbar.

Views

This section has a toolbar with standard buttons. The grid contains a list of the data views for this table.

To edit the properties of an view, double-click its name. To add a view to the list, click Create New. PhixFlow opens the View properties tab.

To remove a view from the table, select the view and click Delete in the toolbar.

Sort Orders

This section has a toolbar with standard buttons. The grid contains a list of the sort orders for this table.

To edit the properties of a sort order, double-click its name. To add a sort order to the list, click Create New. PhixFlow opens the Sort Order properties tab.

To remove a sort order from the table, select the sort order and click Delete in the toolbar.

Errors

This section has a toolbar with standard buttons. See Menu Options and Toolbar Buttons.

When you save changes to the properties of a table or view attribute, PhixFlow validates that the properties are set correctly. If there is an issue with the properties, PhixFlow indicates this with a Model Validation Status of ERROR.

The Errors grid contains a list of the validation checks. For those that failed, the Validation Message indicates which properties need fixing. For example, PhixFlow reports an error if the steam has no Data Retention option set. Double-click on a row to view a full message.

PhixFlow can process data from tables or view attributes that have validation errors. The validation checks help you to configure tables and view attributes so that PhixFlow can continue to run efficiently. For example, PhixFlow reports an error if a table has no Data Retention option set because it can affect performance when all old tablesets are retained,

When a table or view attribute has validation errors, these are also be listed in the Errors section of the application or package to which the table or view belongs.

Relations

This section has a toolbar with standard buttons. The grid displays a read-only list of the relationships that this table has. Double-click a relationship to display it's properties; see Relationship.

Filters

This section has a toolbar with standard buttons. The grid contains a list of the filters that can be applied to this table. You can add filters to view based on this table.

All filters in this list are available in the default view for this table. For views that you create, in the View properties tab → Filters section, you can add filters. The list of available filters is populated by the filters defined for the table.

To edit the properties of a filter, double-click its name. To add a filter to the list, click Create New. PhixFlow opens the Filter properties tab.

To remove a filter from the table, select the filter and click Delete in the toolbar.

In a view grid, the header row has a drop-down list of filters. The drop-down list is populated by the filters that are selected on the view. The filters must first be defined for the table here.

Inputs

This section has a toolbar with Show a Detailed List and Refresh buttons; see standard buttons. In the grid, PhixFlow lists all pipes that connect into the table. You cannot edit this grid.

This list can include pipes that have no input. This occurs if the source table has been deleted or if a model has been moved to a different PhixFlow instance (export/import), leaving behind a referenced table. Any pipes with no input are highlighted in yellow. To resolve pipes with no input you can:

recreate the missing table
import the missing table
keep the connection, if it will be restored when the model is moved to a different PhixFlow instance
delete the pipe, if it is no longer required.

Download Limits

The following properties affect the number of data records a user can download from a view, such as a grid, chart or card; see Download CSV or Excel Data.

Field	Description
Table Download Limit	Enter the maximum number of records that a user can download from a view on this table. If no value is set, PhixFlow uses the default limit set in System Configuration→ System Tuning → Default Download File Limit.
Allow Unlimited Downloads	Untick to restrict all users to the Table Download Limit. Tick to display a User Groups section where you can specify user groups whose members can download unlimited data from a view on this table. For example, members of the Administrators user group may need to download all data.
User Groups	Available when Allow Unlimited Downloads is ticked. Use this section to select the user groups whose members can download an unlimited number of records. This section has a toolbar with standard buttons and User Groups. The grid contains a list of user groups that are exempt from the Table Download Limit. To add a user group to the list: Click User Groups to list all the user groups in the repository. Drag user groups into this list to add them to the role. To remove user groups, use the Delete in the toolbar.

Sections on this page

Learn More

Terminology changes in progress

As part of the redesign of PhixFlow, we are changing the following terms:

dashboard → screen
stream → table
stream attributes → attributes
stream item → record
stream set → recordset
stream view → view
stream item action → record-action
stream action → table-action
driver class → database driver

Data Retention Settings

Use the following options to specify how PhixFlow manages old data when a table-data-delete task runs.

We recommend that you always specify the data retention values for every table you create.
PhixFlow checks that a table has:

either data retention settings (recommended)
or Retain All Data selected.

If no data retention option is set, PhixFlow displays an error in the Errors section, above.

Using Tasks and Task Plans for information about tasks.
Deleting Old Data to see how you can use these values in data management strategies.

Field	Description	What Data is Deleted
Retain All Data	Untick to specify the criteria for keeping data in the Keep... properties below (recommended). Tick to allow old data to accumulate in PhixFlow. Tables with Retain All Data ticked never have their data deleted and the data will accumulate. This can lead to performance issues.
Keep for N Days	Enter the number of days to keep data in the table. The age of data in a recordset is its 'to' date, relative to the 'to' date of the newest valid recordset in the table .	When a table-data-delete task runs for a table and: Keep for X Days only is set, PhixFlow deletes table data that is older than N days. Keep for Y Recordsets only is set, PhixFlow keeps the most recent X recordsets and deletes recordsets that exceed X. both Keep for X Days and Keep for Y Recordsets are set, PhixFlow deletes the table data that meets both conditions. neither Keep for N Days nor Keep for X Recordsets are set, PhixFlow keeps table data indefinitely. This can lead to performance issues.
Keep for X Recordsets	The number of recordsets to keep in the table.
Keep Superseded for N Days	Available when Track Superseded Data is selected. Enter the number of days to keep superseded records in the table data. Remember to keep superseded records for as long as you want the option to roll back the data. For example, when Keep Superseded for N Days is set to 4, you can run roll back on data that was superseded up to 4 days ago. A table-data-delete task removes superseded records older than 4 days, so PhixFlow no longer has the data to be able to roll it back.	In a table where the superseded date is tracked, the table data contains a mixture of active records and records that have been superseded. When a table-data-delete task runs for a table and: Keep Superseded for N Days only is set, PhixFlow deletes data records that were superseded more than N days ago. Keep Superseded for X Recordsets only is set, PhixFlow deletes superseded records from the recordsets that exceed X. both Keep Superseded for N Days and Keep Superseded for X Recordsets are set, PhixFlow deletes the superseded records that meet both conditions. neither Keep Superseded for N Days nor Keep Superseded for X Recordsets are set, PhixFlow keeps superseded records indefinitely. This can lead to performance issues.
Keep Superseded for X Tablesets	Available when Track Superseded Data is selected. Enter the number of recent recordsets that will retain their superseded data records.
Apply Delete Filter	: Tick to open a filter tab where you can set filter conditions; see Filter. PhixFlow applies this filter when it runs a table-data-delete task. Only the records which match the filter are deleted.

Analysis Models

If this item is used by an analysis model, its name is listed here. See the Common Properties page, Analysis Model section for more details.

Advanced

Only change the advanced properties with advice by PhixFlow support.

Field	Description
Advanced Properties	Only use this field with advice from PhixFlow support.
Database View	Use this property if your database administrator wants to query table data in the PhixFlow database. Enter a string in the format `v_xxxx`. When the table is published to the database, PhixFlow creates a view. If the table is deleted, the next system task that runs will clear the associated view from the database. By default, this field is blank and no view is created in the database. See also Configuring Access to Database Views.
Storage Options
Index Scheme	Select an option to determine how indexes on the table are organised. All: indexes on the table are optimised for selecting from all recordsets (non-historied reads). Latest: indexes on the table are optimised for selecting from the latest recordset (i.e. for historied reads). Superseded: indexes on the table are optimised for self-updating tables which have a mostly superseded records. None: no indexes are created on the table. Partitioned: this index scheme is specific to partitioned tables; see Storage Type below. Partitioned tables must use this index scheme, and only partitioned tables can use it.
Storage Type	Select an option to specify how data for the table should be stored: Database: Store the data in a regular table within the PhixFlow database. This is the most common option Database (Partitioned): Store the data in a partitioned table within the PhixFlow database. This option provides improved performance for rollback and retaining very large recordsets. The option is only available if "partitioning" is available within your database installation. In Memory: Data for the table will not be written to the database. This option can be used (for example) when you want to aggregate large amounts of unsorted data which can then be written to a stored table.
Data Generation Options
Start Date	Enter the date on which this table starts or click Show Calendar to select a date. Data will be populated into the table from this date onwards.
Primary Key Generator	This option relates to an actionflow with a save node that inserts a new record into a table. Each new record requires a unique value for the record's primary key. Use this option to specify how PhixFlow generates the primary key value. Internal: PhixFlow generates unique primary key values automatically. This is equivalent to setting the attribute expression to `_NULL`. Sequence: display the Primary Key Generator Sequence option, in which you can select a sequence of values.
Primary Key Generator Sequence	Available when Primary Key Generator is Sequence. Select a sequence to assign a new value to the primary key attribute of a new record; see Sequence. The new record takes the next primary key value in a sequence. This is equivalent to setting the attribute expression to `nextValue("sequenceName"`.
In Memory Cache Size	Enter the size of the cache that will be maintained when you are using an in-memory table. See Manage Unsorted Data Using an In-Memory Stream.
Allow Partial Set Processing	Untick to restrict all users to the Table Download Limit. Tick so that, when analysis reaches the end of a buffer block, it submits the candidate set for processing, even if the next buffer block has a different key.
Prevent Parallel Processing	Available when Period is Transactional. Tick to ensure only a single recordset can be generated at a time even if the table receives several concurrent requests to generate data. This can be useful where you want to make sure that two analysis runs do not attempt to update the same records at the same time e.g. as a result of two people selecting the same records in a view and then hitting the same action button at the same time to process those records.
Run Alone	Tick so that, whenever the analysis engine needs to generate data for this table, it will first wait for all running tasks to complete before it starts. Any additional analysis tasks submitted while this table is waiting to start, or while it is generating data, will wait until this table has completed its analysis before they start.
Key Tolerances	When building a candidate set, data can be grouped together using a specific key value, e.g. Account Number. If the key value is a number, enter a key tolerance to identify numbers within the given tolerance as the same key value.
Default View	Select the default view for the table; see Views for details of creating views on tables.
Last Run Date (Read only)	PhixFlow displays the date and time that analysis was last run for this table. This date is taken from the "to date" of the most recent recordset for this table.
Last Run By	PhixFlow displays the user that last ran analysis on this table.

Description

We recommend that you always enter a description to explain the purpose of this item.

Security Tab

Access Permissions

See the Common Properties page, Access Permissions section.

By default, the permissions to access table data is set in System Configuration → Allow access to data by default. You can add specific user groups to restrict access to the table.

Audit Tab

Audit Summary

See the Common Properties page, Audit Summary section.

Table