Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 9 Next »

Use filters to display or work with a subset of data in a stream.

To add a filter to the data in a stream:

  1. In  the repository, expand the stream.
  2. Right-click on Filters and  Create New  a new filter.

To add a filter to a view of the data in a stream:

  1. In  the repository, expand the stream.
  2. Expand the data view.
  3. Right-click on Filters and  Create New  a new filter.

PhixFlow displays the filter properties.

You can also apply filters on the data directly in a dashboard or view; see Filters on Data Views.

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.

Basic Settings

FieldDescription
NameThe name of the filter.
Private

Available to users with the Create Public Filters privilege.

 Tick to make the filter available only to the user who created it. If this field is not visible to you, the filter is automatically private.

 Untick to make the filter available to other PhixFlow users.

Protect during import

 Untick to allow the filter settings to be changed if this filter is imported from another PhixFlow instance. If the imported configuration does not include this filter, it will be deleted.

 Tick to retain the filter settings if this filter is imported from another PhixFlow instance. To prevent orphaned filters, when a parent stream is deleted by the import, its filters are also deleted.

 More ...

When you have several instances of PhixFlow, for example development and production instances, you may want some item properties to be different for each instance. Usually, when you export from a source instance, then import to a target instance, PhixFlow overwrites item properties with those from the source instance. In the target instance, tick this box to prevent the current setting being overwritten by the source item.

Filter Details

To create a filter, add conditions and clauses.

Field
Description
Condition

Select one of the options

  • Where ALL...
  • Where ANY...

To add more conditions, hover your mouse pointer over this field to display the  Create New button.

 Create New

Hover your mouse pointer over the Condition field to display this button.
Add another condition to your filter.

Clause

Select an option from the list. PhixFlow adds more fields where you can:

  • select how the filter matches (for example, equals, contains, is null)
  • enter a string that the filter uses to match the data. The string can be an expression or a literal string.
 Delete

Hover your mouse pointer over a filter clause to display this button.
Delete the selected clause or condition from the filter. 

 Literal Value

Indicates the value entered is a literal value. Click this icon to treat the value as an expression.

 (Expression String)

Indicates the value entered is an expression. Click this icon to treat the value to a literal string.

Ignore Case   

 Untick so that, for PhixFlow instances running on Oracle or MariaDB (MySQL), the condition only matches strings that have the same capitalisation (case-sensitive).

 Tick so that the condition matches strings that have any capitalisation (case-insensitive). For example "abc" matches "abc", "Abc", "ABC", etc. For case-insensitive filters, there is no difference if the attribute is also indexed. 

Whether or not the check box is ticked by default depends on the underlying stream attribute property tab → Advanced section → Filter conditions are case-independent by default.

This option affects the behaviour of filters for PhixFlow instances running on Oracle or MariaDB (MySQL) databases. 
For PhixFlow instances running on a SQLServer database, filters are always case-independent.
  • No labels