For Microsoft Dynamics NAV to run properly, we also require tables that contain more records to allow multiple values to be used in various scenarios. These values are almost as static as the Singleton tables, although the new records can be created during the lifecycle of the application.
The pattern for these tables is Supplemental & Subsidiary.
The Supplemental & Subsidiary table has a single field Primary Key that is typically called Code; it has the Data type code, and has a length of 10 characters. Values in the Primary Key are manually determined by the application administrators. Normal users of the system have read-only access to these tables.
When the attributes in the table relate to another entity, the reference to this entity can be added as a second primary key.
The other fields in the table contain the specific setup values that are required from a functional perspective, but can also contain references to design patterns, such as the address integration.
The following diagram explains how to implement the Supplemental & Subsidiary Pattern:
The Page objects, connected to these tables are typically the editable List pages. Card pages are only required when the complexity exceeds the number of columns that fit on a screen with a normal resolution.
The Supplemental & Subsidiary pattern is used for Setup tables that have more than one value in the application.