Archiving fields: Overview

Reduce the clutter by archiving fields that contain data that is not actively used.

Normally, the data stored in the field that is archived consists of older data that must be kept because it is important to the organization for reference purposes or for regulatory compliance reasons.

Before you archive fields, you must run the dependency checker. For example, the dependency checker detects whether the field that is being archived is used:

• In private searches and in public searches such as searches that are used to refine role permissions, generate dashboards, and target records in the Begin blocks of workflows.
• In rules that use the field in the Begin blocks of workflows.
• In visibility rules created with the screen builder.
• In workflow blocks such as the Notify block.
• In integrations where the field in a vendor application is mapped to an Oomnitza field.

The dependency checker categorizes the issues that are detected as:

• Warnings
• Blockers

If you get warnings, you can ignore them. However, best practice is to resolve any issues that are detected. For example, if you used the field in a private search, you will get a warning when you archive the field. 

If you get blocker notifications, you must resolve the issues that are detected.