Data dictionary: overview
Connects Protheus structure, presentation and configuration.
Overview
TOTVS defines the dictionary as tables organizing physical structure, presentation, parameters and questions. A physical field list therefore does not describe every behavior of a registration routine. Before customizing, identify the existing rule and supported maintenance tool. The example is a teaching record for a fictional field rather than a dictionary change command, stating type, length and purpose for review. (TOTVS, n.d., ref. 1)
Commented example
// Editorial proposal; not a dictionary execution script.
Field: ED_COD
Type: character
Length: 10
Purpose: fictional test identifier
Validation: define under the process contractReview record without changing metadata or tables. Under review: editorial example neither compiled nor run in Protheus. Check includes, release, RDD and context before testing.
- Do not edit control tables through SQL to reproduce this example. Distinguish functional requirements from technical properties.
- Under review: editorial example neither compiled nor run in Protheus. Check includes, release, RDD and context before testing.

Comments
There are no approved comments yet.
Sign in with Google or Microsoft to comment.