5.12.3.1.9. Classification
according to CNSORDERNO / CNSTYPECODE
5.12.3.1.9.5.
TestMeta: General for order number or type code
|  |
| Prev | Next |
5.12.3.1.9. Classification
according to CNSORDERNO / CNSTYPECODE
5.12.3.1.9.5.
TestMeta: General for order number or type code
| |
| Prev | Next |
Set the options Test value ranges and Test order number for uniqueness.
To avoid warnings/errors in the TestMeta (see Section 6.8, “Error Messages: Problem - Solution (PARTproject)”) ...
... the variable with order number / type code has to have a value for each row.
... variable with order number [Variable with order number] and/or variable with type code must be set uniquely, otherwise an ERROR is displayed.
Excluded are a) hidden projects and b) projects, which are in hidden folders and are not used as linked project.
... the number must either be found via a mapping file graphlookup.map or a ReverseConfig file pnoreverse.cfg or via the Lucene index. The corresponding setting is automatically set in a key in the project file.[46]
That means when testing old catalogs where this setting has not been performed yet, an error message will show up.
The modeler must therefore carry out the resolution check [Resolve check]. The corresponding setting can be set automatically there. Details on the resolution check [Resolve check] can be found under Section 5.8.2.1.16.26, “ Reverse Search - Resolve check (automatic) ”.
Basic information on TestMeta can be found at Section 5.8.2.1.12, “ Test project / Test directory ”.
