Skip to content

Advanced Administration

Validate Custom Attribute Metadata

It is possible to run one or several attributes through a diagnostic test before trying to publish. This test checks the integrity of the configuration so that it can be published. This is typically useful when configurations have been transferred (exported/imported) between environments. Also, after an application upgrade, it can be useful to validate the configuration before trying to publish the object.

  1. In the Custom Attributes page, select one or several attributes to be validated.
  2. In the Page commands for the selected one attribute, select Validate.
  3. User will get notified on the validation result for the selected attribute.

Cleanup Custom Attribute Data

When unpublishing an entity the view and package are removed but the table remains. The reason for this is to make it possible to update the configuration and republish without losing any stored data. In situations where the Entity is unpublished to completely remove it, a cleanup operation must be performed. There are two different cleanup methods available.

Remove Unused Custom Data

Unused custom data are columns residing in the deployed table that is no longer published. This occurs when an attribute has been published earlier but is now removed or unpublished. if this operation is run, these columns are removed from the table. The rest of the table will be kept with all currently stored data intact. This operation does not require the Entity to be unpublished.

Remove All Custom Data

This operation will drop the entire table and all stored data with it. This operation requires the entity to be unpublished.

Note: Cleanup removes the data completely. Unless you have a backup of the data, there is no way to recover deleted data.

Cleanup Custom Entity Data

When unpublishing a entity the view and package are removed but the table remains. The reason for this is to make it possible to update the configuration and republish without losing any stored data. In situations where the entity is unpublished to completely remove it, a cleanup operation must be performed. There are two different cleanup methods available.

Remove Obsolete Table Columns

Unused custom data are columns residing in the deployed table that is no longer published. This occurs when an attribute has been published earlier but is now removed or unpublished. if this operation is run, these columns are removed from the table. The rest of the table will be kept with all currently stored data intact. This operation does not require the entity to be unpublished.

Remove Table

This operation will drop the entire table and all stored data with it. This operation requires the entity to be unpublished.

Note: Cleanup removes the data completely. Unless you have a backup of the data, there is no way to recover deleted data.