/plugadvpl:trace

What problem does it solve?

It solves the problem of figuring out what breaks (or what is affected) when you change a Protheus ADVPL/TLPP entity like a field, function, or table, without having to run multiple separate analysis commands and correlate their outputs manually.

Core Features & Use Cases

• Unified cross-universe impact trace across sources, SX metadata, and workflow/execauto/docs in one aggregated result.
• Automatic entity type detection (field, function, table, file, parameter, or pergunta) with an override when the heuristic is ambiguous.
• Graph depth exploration with controllable BFS depth and per-edge hit limits to reduce noise and explosion.
• Use cases: diagnose regressions from a field change, identify who writes to a table, and determine whether a function is unused or only triggered indirectly.

Quick Start

Run /plugadvpl:trace A1_COD to get a unified trace of every reference and workflow impact related to the field A1_COD.