Master-detail relationship
Master-detail relationship between data blocks and associated screen parts.

Dynamic tree view loading
Child tree nodes are loaded from the server when the user expands the parent tree node.

Required fields checking
Automatically checking that all data fields marked as required are filled in by the user. Invalid fields are highlighted on the screen and a custom error message can be shown to the user.

Value range checking
Checking that the input value is according to the specified data range. Invalid fields are highlighted on the screen and a custom error message can be shown to the user.

Numeric value input checking
Checking that text in the numeric fields can be converted to numeric values. Invalid fields are highlighted on the screen and a custom error message can be shown to the user.

Field format checking
Checking that the user input is according to custom field format (optional). Invalid fields are highlighted on the screen and a custom error message can be shown to the user.

Master-detail in lookup fields
Lookup lists can be filtered with master-detail relationship. For instance, a form can contain two lookup fields: country and city. When a country is selected, the city drop-down list will only show the cities of that country.

Referential integrity checking
Checking that data in related data blocks are part of an intergral part of SampleNavigator.

Enabling/disabling commands
Commands on the screen and the associated user interface controls (menu items and toolbar buttons) can be enabled or disabled depending on the current data context.

Keyboard navigation
The user can navigate across controls on the screen using the keyboard only, i.e. without the mouse. Hotkeys can be used for quick navigation or execution of commands.