Working with existing datasets
Validating a dataset
To validate a dataset at any time, select Actions > Validate from the navigation pane. A generated report provides the results of the validation. From the validation report, you have the option to update the reported validation status by clicking the Revalidate button, or to click the Reinitialize validation report button to clear the current validation report associated with the dataset in order to be able to rerun a full validation from scratch.
Validations of data can also be run at the table level by navigating to the desired table from the navigation pane, then selecting Actions > Validate from the workspace.
See Validation for detailed information about incremental data validation.
Duplicating a dataset
To duplicate an existing dataset, select it from the 'Select dataset' 
menu in the navigation pane, then select Actions > Duplicate.
Deactivating a dataset
When a dataset is activated, it will be subject to validation. That is, all mandatory elements must be defined in order for the dataset to be valid. If a dataset is active and validated, it can be safely exported to external systems or to be used by other Java applications.
If a dataset is missing mandatory elements, it can be deactivated by setting the property 'Activated' to 'No' from Actions > Information.
Managing dataset permissions
Dataset permissions can be accessed by selecting Actions > Permissions in the navigation pane.
Permissions are defined using profile records. To define a new permissions profile, create a new record in the 'Access rights by profile' table.
See also
Profile | Defines the profile to which these permissions apply. |
Restriction policy | If 'Yes', indicates that when the permissions defined here are more strict than otherwise defined, these permissions are respected. This is contrary to the default where the most permissive rights defined take precedence. |
Dataset actions | Specifies the permissions for actions on the dataset. |
Create a child dataset | Indicates whether the profile can create a child dataset. Inheritance also must be activated in the data model. |
Duplicate the dataset | Indicates whether the profile can duplicate the dataset. |
Delete the dataset | Indicates whether the profile can delete the dataset. |
Activate/deactivate the dataset | Indicates whether the profile can modify the Activated property in the dataset information. See Deactivating a dataset. |
Create a view | Indicates whether the profile can create views and hierarchies in the dataset. |
Tables policy | Specifies the default permissions for all tables. Specific permissions can also be defined for a table by clicking the '+' button. |
Create a new record | Indicates whether the profile can create records in the table. |
Overwrite inherited record | Indicates whether the profile can override inherited records in the table. This permission is useful when using dataset inheritance. |
Occult inherited record | Indicates whether the profile can occult inherited records in the table. This permission is useful when using dataset inheritance. |
Delete a record | Indicates whether the profile can delete records in the table. |
Values access policy | Specifies the default access permissions for all the nodes of the dataset and allows the definition of permissions for specific nodes. The default access permissions are used if no custom permissions have been defined for a node. The specific policy selector allows granting specific access permissions for a node. The links "ReadOnly", "ReadWrite", and "Hidden" set the corresponding access levels for the selected nodes. It is possible to remove custom access permissions using the "(default)" link. |
Rights on services | This section specifies the access permissions for services. A service is not accessible to a profile if it is crossed-out. |
User guide table of contents