SX Configuration

Overview

Templates and validation rules for generating Protheus data dictionary configuration scripts. Covers SX3 (fields), SIX (indexes), SX1 (report questions), SX5 (generic tables), and SX7 (triggers).

When to Use

• Creating new custom fields for a table
• Defining indexes for custom tables
• Setting up report parameter questions
• Creating generic lookup tables
• Configuring field triggers

SX3 — Field Definition

Required Fields

Validation Rules

Common Validations

Common Pictures

SIX — Index Definition

Required Fields

Rules

• Index 1 is ALWAYS the primary key (FILIAL + unique field)
• FILIAL must be the first component of every index
• Nickname must be unique within the table
• Order must be sequential starting from 1

SX1 — Report Questions

Required Fields

Rules

• Questions come in pairs for range filters (De/Ate)
• Type D always has size 8
• Default for "De" date: Space(8) or first day of month
• Default for "Ate" date: dDataBase or last day of month
• Default for "De" char: Space(size)
• Default for "Ate" char: Replicate("Z", size)
• If combo (C), X1_DEF01 contains the default option value
• X1_GSC: G=Get (text input), S=Select (not common), C=Combo

SX5 — Generic Tables

Required Fields

Rules

• Table code: 2 uppercase characters (use Z prefix for custom: ZA, ZB, ZZ, etc.)
• Key: 2 characters, sequential (01, 02, 03...)
• To use in code: GetSX5("ZZ", "01") or X5DESCRI("ZZ", "01")

SX7 — Triggers

Required Fields

Rules

• Triggers fire when source field changes
• Posicione() is the standard function for lookups
• Always include xFilial() in the seek expression
• Sequence allows multiple triggers on the same field

Output Format

Scripts are formatted as key-value blocks, one field definition per block, separated by dashes. This format is human-readable and can be used as reference for manual configuration in the Configurador or for import scripts.