Question 280
A form shows a friendly label for a choice field but an import sends an unknown underlying choice value. Which TWO complementary steps supply the appropriate administrative response and the evidence needed to verify it? Select TWO.
Explanation
Correct Answers
Configure dictionary entries and field types for their intended semantics, including length, mandatory behavior and choice/reference constraints, without assuming a form-only change modifies storage. Dictionary settings define schema characteristics that can affect many views and integrations; changing a label does not change the stored data type. Verify prerequisites with: Inspect sys_dictionary field definition, column type, choice list, inherited entry or override, default value, and existing data before schema changes. Scenario: A form shows a friendly label for a choice field but an import sends an unknown underlying choice value.
Inspect sys_dictionary field definition, column type, choice list, inherited entry or override, default value, and existing data before schema changes. Dictionary settings define schema characteristics that can affect many views and integrations; changing a label does not change the stored data type. The appropriate response is: Configure dictionary entries and field types for their intended semantics, including length, mandatory behavior and choice/reference constraints, without assuming a form-only change modifies storage. Scenario: A form shows a friendly label for a choice field but an import sends an unknown underlying choice value.
Incorrect Answers
Define a reference field to a suitable target table and validate stored sys_id and display-value behavior, rather than treating a text label as a reliable relationship key. This step may apply to Reference fields and display values in the data dictionary but is not one of the complementary requirements in this case. The intended pair is: Configure dictionary entries and field types for their intended semantics, including length, mandatory behavior and choice/reference constraints, without assuming a form-only change modifies storage. Together with: Inspect sys_dictionary field definition, column type, choice list, inherited entry or override, default value, and existing data before schema changes. Scenario: A form shows a friendly label for a choice field but an import sends an unknown underlying choice value.
Inspect base and extended table definitions, inherited dictionary fields, expected record lifecycle, roles, and reporting requirements. This step may apply to Table extension and inherited task fields but is not one of the complementary requirements in this case. The intended pair is: Configure dictionary entries and field types for their intended semantics, including length, mandatory behavior and choice/reference constraints, without assuming a form-only change modifies storage. Together with: Inspect sys_dictionary field definition, column type, choice list, inherited entry or override, default value, and existing data before schema changes. Scenario: A form shows a friendly label for a choice field but an import sends an unknown underlying choice value.
The intended layout appears only in the proper interface with existing record operations, ACLs and user tasks still functioning. This step may apply to Configurable form and workspace layout changes but is not one of the complementary requirements in this case. The intended pair is: Configure dictionary entries and field types for their intended semantics, including length, mandatory behavior and choice/reference constraints, without assuming a form-only change modifies storage. Together with: Inspect sys_dictionary field definition, column type, choice list, inherited entry or override, default value, and existing data before schema changes. Scenario: A form shows a friendly label for a choice field but an import sends an unknown underlying choice value.


