The key pane can hold different columns. Everything which can be part of a column can be supported in fields.
Key and cylinder data is very similar, so each field needs to be prefixed with KEY to make a distinction to the cylinder data.
Field |
Description |
KEY.Name |
Name of the key article / programming-key article |
KEY.Code |
Code of the KMC (repeated for the key article/instance) Name of the programmingkeygroup (repeated for the programmingkey article/instance) Name of the cliqkeygroup |
KEY.UserType |
UserType of the KMC. |
KEY.FuncType |
Functional type of the KMC. |
KEY.Marking1 |
Marking1 of the key instance / programmingkey instance |
KEY.Marking2 |
Marking2 of the key instance / programmingkey instance |
KEY.Marking3 |
Marking3 of the key instance / programmingkey instance |
KEY.Marking4 |
Marking4 of the key instance / programmingkey instance |
KEY.Quantity |
Quantity of the instances in the KMC / programmingkeygroup (total quantity of instances with status = NEW) |
KEY.ProducedQuantity |
Quantity of the instances in the KMC / programmingkeygroup (total quantity of instances with status != NEW) |
KEY.ProdSetting |
Production setting of the key article / programmingkey article |
KEY.Product |
Product name of the configuration of the key article |
KEY.ProductCode |
Product code of the configuration of the key article |
KEY.ATTRValue.xxx |
Attribute value part of the configuration of the key article for the attribute for which the attribute code matches the ‘xxx’ E.g. KEY.ATTRValue.Color Subtract ‘KEY.ATTRValue.’ and match the code for the attribute. |