Interface datasets
What is an Interface dataset?
You can arrange a collection of columns of one template dataset to create an interface dataset… a form that displays data to the user and can allow him or her to interact with the data (update, delete, add… etc.)
Interface datasets can be displayed into two modes:
Linking datasets
You can choose to link one ‘list-mode dataset’, to another ‘record-mode dataset’ to allow the user to select (in the list) the record to update.
To do this, you can proceed as follows:

Creating a sub-datasets
Data displayed into a list-mode dataset may depend on a choice or a selection done outside of the dataset itself.
For example, we created, say, a list-mode dataset that displays menu commands… and another that displays menu themes.
Now, suppose that we want the menu commands dataset to display only menu commands of a selected theme.
To do this, we simply set the theme_id field as the ‘Parent field’ of the menu commands dataset.

The menu commands dataset acts then as a sub-dataset: i.e. it will not display any data until it receives a value for its parent field (in this case ‘theme_id’)

Le contenu d’une liste d’informations peut dépendre d’un critère extérieur.
Dans le formulaire en cours, pare exemple, le contenu de l’onglet ‘Propriétés du set’ affiche seulement la liste des propriétés du dataset sélectionné.
This property can be used to logically link different datasets of a form (dataFrame)

For more information about linking form datasets: see dataFrame introduction.
Controlling the interface
Fields of an interface dataset are displayed as controls that you choose according to each field’s significance and requirements.
Use the field record to:

Use the dataset properties record (not available in the demo version) to:

Use the field’s attributes record (not available in the demo version) to:
Dynamically filtering dataset information
This option will be available in the demo version in the near future

You can dynamically filter dataset information according to criteria related to predefined constants or to a user’s session-specific value.
Use the ‘Main filter’ tab to:

Filter important note:
If you decide to apply more than one filter type for the same field (if you decide, for example, to apply a constant, a session variable and an application variable)… simpleSite handles priorities as follows:

This priority order can be used to compose criteria dynamic values (session and / or application variables) with the constant as a default value.
Dynamically setting session’s and application’s variables
This option will be available in the demo version in the near future

As mentioned above, simpleSite allows you to dynamically create session’s and / or application’s variables as needed.
simpleSite also allows you to dynamically assign values to these variables using interface datasets.
Use the Session variables tab to:
Manage dataset access authorization
This option will be available in the demo version in the near future

To display or use an interface dataset, a user must be authorized to do so.
Access authorizations allow you manage user’s permissions to interact with the dataset in the following domains:
  • rd read data permission;
  • wr write permission;
  • ad add record permission;
  • del delete records permission;

Permissions can be assigned through:

Use the Authorization tab to manage permissions for the currently selected dataset.

You can manage permissions in more exhaustive mode by accessing the specific Authorization management form.