Field No., Scheduler Subjob Filter
Note - Subjobs that have the Replication Method by Action cannot be filtered.
The following table explains the filter functions and shows where they can be applied:
Filter name | Filter function/properties | Replicator | Data Director | Value1 | Value2 |
---|---|---|---|---|---|
1. Const | An exact value is entered in Value1 to be used as filter. Examples: a date, text, code such as Dept. code:FOOD |
Yes | Yes | Yes | No |
2. Filter | Database specific filter. For example when replicating from Navision to Navision you can use wild characters (*,?,|,@ etc). Note: Only supported for Navision. Example: Food|Clothes |
Yes | Yes | Yes | No |
3. From-Location | The From-Location in the job is used as the filter for the field in question. Example: Enter the Transact. Store No. the type From-Location |
Yes | Yes | No | No |
4. To-Location | Same as in From-Location but in the Data Director there can be more than one To-Locations. Rarely used with the Data Director because it reduces performance |
Yes | Yes | No | No |
5. | Less than: Filters on jobs with a value lower than the one specified in Value1. | No | Yes | Yes | No |
6. > | More than: Filters on jobs with a value higher than the one specified in Value1. | No | Yes | Yes | No |
7. [..] | Range: Filters for jobs that fall within the range specified in Value1 and Value2. | No | Yes | Yes | Yes |
8. min | Filters for the job with the lowest value. | No | Yes | No | No |
9. max | Filters for the job with the highest value. | No | Yes | No | No |
Note: As concerns To-Location filters, bear in mind the following:
- As many packages are created as there are receivers.
- It is not recommended to use this filter for jobs that have many subjobs.
- Subjobs with To-Location filters should preferably not be kept with other subjobs because of the reduced performance, but sometimes this may be necessary for the sake of consistency.
Filters 5-9 are plug-in independent. They can be used where Filter (2) can not be used.