powered by CADENAS

Manual

Manual

3.2.16.6. TestMeta: General for Order number or Typecode

Set the options Test value ranges and Test order number for uniqueness.

In order to avoid warnings/errors in TestMeta (see Section 6.8, “Error Messages: Problem - Solution”) ...

  • ... the variable with order number / type code has to have a value for each row.

  • ... Variable with order number and/or Variable with type code has to be uniquely set. Otherwise an ERROR is displayed. If, for example, TYPE has been classified, which occurs in every table row, this is an error and will be shown by TestMeta.

    Excluded are a) hidden projects and b) projects, which are in hidden folders and are not used as linked project.

  • ... the number has to be findable either via a ReverseConfig or via Lucene index (for this also the setting under Index order numbers dependent on value ranges serves [see Section 3.2.16.3, “Index order numbers dependent on value ranges ”]).

    That means for old catalogs, where the flag is not set yet, that an error message will appear, if there are value ranges and no ReverseConfig is findable or the value range cannot be resolved (and so cannot become part of the Lucene index). So the modeler has to set the flag on "Yes" or apply a ReverseConfig to avoid the error message.

    If value ranges exist, it has to be checked, of which category they are.

    1. Config limit is kept

      -> Order number have to be indexed, meaning the option Index order numbers dependent on value ranges has to be activated.

    2. Config limit is not kept

      -> A ReverseConfig has to be used, meaning the option Index order numbers dependent on value ranges has to be deactivated.

Basic information on TestMeta can be found under Section 5.8.2.1.12, “ Test project / Test directory ”.