Skip to content
tcli

Batch LOVs

See the config-artifact guide for how to add, register, and deploy batch LOVs. This page covers how to structure and name them.

Unlike most config artifacts, batch LOVs are not a flat directory of files. configuration/batch_lovs contains one subdirectory per LOV, and files are never placed directly in the source directory. tcli lint enforces this layout.

Per-LOV directory

Section titled “Per-LOV directory”

Each LOV lives in its own directory named after the LOV. Inside it:

  • One or more content files whose base name matches the directory name, with a .xml, .xlsx, or .xlsm extension.
  • A required lang/ subdirectory holding the localised value files. No other subdirectories are allowed.
configuration/batch_lovs/
  Emx4Lov/
    Emx4Lov.xlsx
    Emx4Lov.xml
    lang/
      Emx4Lov_en_US.xml
      Emx4Lov_de_DE.xml

Language files

Section titled “Language files”

Files inside lang/:

  • Must be .xml.
  • Must be prefixed with the LOV name followed by an underscore (<lov>_), followed by a non-empty locale suffix.
  • May not be nested in further subdirectories.

For a LOV named Emx4Lov, valid language files are Emx4Lov_en_US.xml, Emx4Lov_de_DE.xml, and so on.