advpl-dicionario-sx

Map Protheus SX dictionary tables governing fields, validations, triggers, and F3 lookups.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/JoniPraia/plugadvpl --skill advpl-dicionario-sx
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: advpl-dicionario-sx
Source: https://github.com/JoniPraia/plugadvpl/tree/main/skills/advpl-dicionario-sx
Command: npx skills add https://github.com/JoniPraia/plugadvpl --skill advpl-dicionario-sx

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you understand, troubleshoot, and safely implement Protheus SX dictionary behavior (SX1/SX3/SX7/SXB/SX6) without scattering logic across source code or risking inconsistent customizations.

Core Features & Use Cases

  • SX documentation for practical changes: explains what each SX table controls (questions, fields, triggers, parameters, F3 lookups, indices, folders) and how they interact at runtime.
  • Field-level reasoning and impact analysis: supports workflows to find why a field appears/disappears, why a trigger fires, and what sources reference a given field (via plugadvpl impact/trigger commands).
  • DX-friendly customization guidance: provides actionable guidance for authoring validations (X3_VALID), conditional editing (X3_WHEN), gatilhos (SX7), and F3 lookups (X3_F3), including safety notes about encoding and “do not edit SX directly in DB” practices.
  • DX-to-implementation mapping: gives a structured mental model and a “map” of SX tables so you can translate business requests into correct dictionary updates.

Quick Start

Ask: "Use /plugadvpl:impacto to find every ADVPL reference and dictionary rule affecting the Protheus field A1_COD, then summarize likely causes of unexpected behavior."

Frequently Asked Questions about advpl-dicionario-sx

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
Why does a Protheus field not appear on the screen and how do SX3 rules control it?

Protheus field visibility is controlled by SX3 dictionary rules, specifically X3_USADO and X3_WHEN settings. Analyzing these configurations helps diagnose why a field is missing from the user interface or restricted from editing.

How do I safely create custom SX7 triggers and X3_VALID rules in Protheus?

To safely create custom SX7 triggers and X3_VALID rules, you should use upgrade-safe dictionary workflows and avoid editing SX tables directly in the database. Properly encoding these rules ensures consistent Protheus behavior during system updates.

What is the best way to perform an impact analysis on a Protheus ADVPL field?

The best way to perform impact analysis on a Protheus ADVPL field is by running structured discovery commands to find every reference and dictionary rule affecting it. This cross-source analysis reveals unexpected behaviors caused by validations or triggers.

Can I use SX CSV exports to diagnose F3 lookup issues in Protheus?

Yes, you can ingest SX CSV exports to safely interpret and diagnose F3 lookup issues in Protheus. This workflow maps SXB dictionary behavior and X3_F3 configurations without risking direct database modifications.

Do I need to understand SX1 and SX6 tables to troubleshoot Protheus parameter behavior?

Yes, understanding SX1 and SX6 tables is necessary to troubleshoot Protheus parameter behavior. SX1 governs programmed questions and SX6 controls internal parameters, both of which directly influence application logic and runtime execution.

Protheus trigger-driven updates are not firing, what SX7 limitations should I check?

If Protheus trigger-driven updates are not firing, check SX7 limitations and configurations like X7_REGRA. Verifying the trigger rule syntax and execution order helps diagnose why the expected field updates are failing during runtime.