Element Filtering Settings
The Element Filtering Settings section allow you to configure a general filter condition, to exclude/include some specific transfers. This additional filtering option can be used for getting only those transfers with an Attribute evaluated with a specific value (e.g. MATERIALCODE = X). The user could configure the additional filter according to the table below:
Element Filtering Settings Available Options
| Input Box | Description |
|---|---|
| Attribute | This combo box contains the name of the Attributes of the templates selected in the main Template Checked-List Box. By default, the selection of this field in “\<None>”. By selecting “\<None>”, the filter option is disabled, meaning that all the transfers selected in the general section will be used by the DR for the summary calculation.In Case another Attribute name different than “\<None>”, the selected Attribute will be used in the filtering condition evaluation. |
| Condition | This field is enabled only when an Attribute different from “\<None>” is selected. User can select among one of the following condition check:EqualNot EqualGreaterGreaterOrEqualLessLessOrEqualLike (included within the value)Not Like (not included within the value) |
| Value | This field is enabled only when an Attribute different from “\<None>” is selected. User can specify the value for testing the condition. The user may insert directly a value or can insert a name of the current Element with the prefix “@” (this setting will get the value from Attribute value). For instance, if the use specifies @MATERIAL, the Data Reference will pick-up the value of the Attribute MATERIAL of the current Element where the DR is configured. The Data Reference checks for circular references, so the same Attribute name will be discarded. Attribute with BAD values will be discarded, meaning that the condition will be every time considered FALSE and value discarded from calculation (leading every time a zero result).In this version of the Data Reference, there is no decimal separator management. So, in this respect, if the user wants to compare a value with decimal digit, the only solution is creating an Attribute in the same Element with double/float type, set up manually the value, and then use the @ATTRIBUTE notation introduced above.Additionally, user may specify some KEYWORDS for picking-up additional values. Here below the list of available keywords supported by Data Reference:@ELEMENTNAME: Name of the actual element (where the DR is configured)@ELEMENTDESC: Description of the actual element (where the DR is configured)@TRANSFERNAME: Name/ID of the transfer@TRANSFERDESC: Description of the transfer@TRANSFERSOURCE": Name of the source Element of the transfer@TRANSFERDEST": Name of the destination Element of the transfer |
Note:
The filtering condition works with either Numeric and String attributes. Depending on the filter configuration, Pimsoft suggests using the following checks:
- Equal and NotEqual for STRING, BOOL and INTEGER. For FLOAT/DOUBLE use only with zero value since there’s no truncation, so some rounding in the decimal digits are expected.
- Greater/GreaterOrEqual/Less/LessOrEqual for all numeric types only. Avoid the STRING Attributes combined with this checks.
- Like and NoLike use only STRING attributes. Avoid the usage of these conditions in conjunction with all numeric types.