Override filtering behavior

This is the official documentation of the @forestadmin/agent Node.js agent.

You may want to read about the following topics before using those features:

• Unlocking filtering, scopes, and segments on the UI

• Structure of a ConditionTree

• List of all filtering Operators

• Operator equivalence system

Disabling operators

Disabling filtering can be made without any code in the field settings.

Substitution

Operation substitution can be used for two motives:

• Performance: provide a more efficient way to perform a given filtering operation

• Capabilities: enable filtering on a computed field or other non-filterable fields

collection.replaceFieldOperator('fullName', 'Equal', (value, context) => {
  const [firstName, ...lastNames] = value.split(' ');

  return {
    aggregator: 'And',
    conditions: [
      { field: 'firstName', operator: 'Equal', value: firstName },
      { field: 'lastName', operator: 'Equal', value: lastNames.join(' ') },
    ],
  };
});

Operators to support to enable the search

Column Type	Operator to support
Number	Equal
Enum	Equal
String	IContains OR Contains OR Equal
Uuid	Equal

You can use the replaceFieldOperator method to unlock the operators.

Emulation

Filtering emulation allows making fields filterable automatically. It is a convenient way to get things working quickly for Collections that have a low number of records (in the thousands at most).

This emulation forces the Agent to retrieve all the Collection records and compute the field values for each one of them. As a consequence, filtering emulation performance cost is linear with the number of records in the Collection, so activate it sparingly and with great care.

// Add support for all operators
collection.emulateFieldFiltering('fullName');

// Add support for a single operator
collection.emulateFieldOperator('fullName', 'Equal');