This section describes the configuration options around extending the claim transaction tables and external claims data with field and / or record definitions.

Dynamic fields and records that extend a claim transaction table or external claims data behave slightly different from their counterparts that extend claims, configuration and reference data. These fields are meant to keep a true copy of whatever information they store. For this reason there are no validations. Dynamic fields and records usages on claim transaction tables or external claims data

• Ignore any field validation logic , that may be configured on the field definition

• Can not be set up as mandatory

• Can not be set up as conditional

• Can not refer to a flex code definition

• Are not time valid

Adding Dynamic Fields and Records

To add a dynamic field to a repository or external data entity, the dynamic field must be defined and then a dynamic field usage must be created to associate the dynamic field definition with the entity. A dynamic field definition may be added to more than one repository or external data entity.

To add a dynamic field to a repository or external data entity, create a dynamic field usage with the following details.

Field	Description
Table	The table that is extended by the field of record
Field Usage Name	Field or record name in the object model and integration points
Display Name	Header displayed in the user interface
Sub Type	Field or Record
Field Definition	The field definition, i.e., the data type, length and decimals
Record Definition	The record definition
Display Sequence	The position of the field or record in the user interface
Multiple Values?	Is it possible to store more than one value? Can only be set for dynamic records, not for dynamic fields.
Display in Overflow?	This indicates whether the dynamic field should be shown in the overflow area in a multi record block
Number format type	The format in which a numeric dynamic field should be displayed