Advanced Administration

Contents

• View Generated/Published Source
• Validate Custom Attribute Metadata
• Cleanup Custom Field Data
• Cleanup Custom Logical Unit Data

View Generated/Published Source

It is possible to get a view of the source that is or will be deployed when publishing.

1. Navigate to the custom objects administration page, and select the logical unit of interest
2. In the context menu, select View -> Generated/Published Objects...

• Generated objects
  Will show the database objects as they are generated according to the currently saved configuration.
• Published objects
  Will show the database objects as they are deployed into the database.

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 objects administration page, select one or several attributes to be validated.
2. In the context menu for the selected attributes, select Validate...
3. In the Validate Custom Field Attributes dialog that opens, validate all attributes at once or one by one.

Cleanup Custom Field Data

When unpublishing a logical unit the view and package is 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 logical unit is unpublished with the intention 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 are 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 logical unit to be unpublished.

Remove All Custom Data

This operation will drop the entire table and all stored data with it. This operation requires the logical unit 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 Logical Unit Data

When unpublishing a logical unit the view and package is 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 logical unit is unpublished with the intention 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 are 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 logical unit to be unpublished.

Remove Table

This operation will drop the entire table and all stored data with it. This operation requires the logical unit 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.