Fields
A Field is the fundamental unit of data capture in the Partial Locking Framework. Fields can be text, numbers, dates, picklists, references, or specialized components such as calculated expressions or file uploads. The editability and upgrade behavior of a field are governed by its lock state. Fields may originate from the Source Tenant or be created locally in the Destination Tenant.
Locking Behavior
The lock state of a field is defined at the source level on the Partial Lock Preference page.
-
Unlocked (Custom) – Created in the destination tenant.
-
Unlocked – Originates from the source tenant but has no lock restrictions.
-
Partially Locked – Editable only in specific, controlled areas.
-
Locked – Fully protected from modification.
If a field is associated with multiple installed applications, the latest update from any source determines its effective lock status.
Tenant Admin Permissions
Tenant Admin permissions on fields are scoped based on their lock state. The table below lists the supported actions.
Object-Level Object Actions
|
|
Built on Destination Tenant |
Built on Source Tenant & Pushed to Destination Tenant | |
|---|---|---|---|
|
Action/Property |
Unlocked (Custom) Field | Partially Locked Field | Locked Field |
|
New Field |
|
|
|
|
New Formula Field |
|
|
|
Field-Specific Actions & Properties
|
|
Built on Destination Tenant |
Built on Source Tenant & Pushed to Destination Tenant |
||
|---|---|---|---|---|
|
Action/Property |
Unlocked (Custom) Field | Unlocked Field | Partially Locked Field | Locked Field |
| Clone |
|
|
|
|
| Delete |
|
|
|
|
| Move |
|
|
|
|
| Validation |
|
|
|
|
| Events |
|
|
|
|
| Change Label |
|
|
|
|
| Convert Field |
|
|
|
|
| Change Integration Name |
|
|
|
|
| View Settings (Header, Size, etc.) |
|
|
|
|
| Default Value |
|
|
|
|
| Field-Level Help |
|
|
|
|
Property-Specific Actions & Properties
|
|
Built on Destination Tenant |
Built on Source Tenant & Pushed to Destination Tenant |
||
|---|---|---|---|---|
|
Action/Property |
Unlocked (Custom) Field | Unlocked Field | Partially Locked Field | Locked Field |
|
Index this field as part of the text search engine. |
|
|
|
|
|
Track all changes to this field in each record's Audit Trail for a complete historical log. |
|
|
|
|
|
Do not allow duplicate values in this field. |
|
|
|
|
|
This field allows inline editing from view pages by clicking on icon. |
|
|
|
|
|
Allow filtering by this field in List Views |
|
|
|
|
|
Always require a value in this field in order to save a record |
|
|
|
|
|
Store values in an encrypted format. |
|
|
|
|
Field Type: Calculated Field (Formula, Expression, Template where applicable)
|
|
Built on Destination Tenant |
Built on Source Tenant & Pushed to Destination Tenant |
||
|---|---|---|---|---|
|
Action/Property |
Unlocked (Custom) Field | Unlocked Field | Partially Locked Field | Locked Field |
|
Return Type |
|
|
|
|
|
Edit Code |
|
|
|
|
|
View Code |
|
|
|
|
|
Dependencies |
|
|
|
|
|
Compute Dependency |
|
|
|
|
|
Validate Formula |
|
|
|
|
|
Debug Formula |
|
|
|
|
|
Test Query |
|
|
|
|
|
Log |
|
|
|
|
Field Type: Document Template
|
|
Built on Destination Tenant |
Built on Source Tenant & Pushed to Destination Tenant |
||
|---|---|---|---|---|
|
Action/Property |
Unlocked (Custom) Field | Unlocked Field | Partially Locked Field | Locked Field |
|
Default Template |
|
|
|
|
|
Popup-window |
|
|
|
|
Super Admins have full administrative control over all the fields, regardless of their lock status. This includes the ability to preview, clone, synchronise, rename, delete, and modify.
If a Super Admin modifies properties that are restricted for Tenant Admins, the component continues to remain on the upgrade path. These changes are treated as temporary overrides and will be replaced by the source during the next application upgrade.
Upgrade Compatibility
When a permitted change is made to a Partially Locked Field, the system automatically sets a Modified flag. This flag indicates that the field has diverged from its source version and influences upgrade behaviour. This information is displayed in the fields information section within the Object definition page.
Restoring Upgrade Path
To revert a Partially Locked Field to its original state, use the Restore Upgrade Compatibility action. This is available only for fields marked as Modified components.
The Restore Upgrade Compatibility option is visible for all installed and modified fields. However, for unsupported fields, its functionality may vary — it might work in some cases and not in others.
To restore the modified field to its original state, do the following:
-
Navigate to the list of fields from the Object Definition page.
-
From the desired field that needs to be restored and click Restore Upgrade Compatibility.
-
A confirmation dialogue indicating that this action is irreversible. Confirm and proceed to restore the modified field to its original state, and the Modified flag is cleared.
-
During the next upgrade, all local configurations are overwritten, and the field is restored to its source version.
Application Upgrade Behaviour on Fields
During an application upgrade, the order of fields in the destination tenant is updated based on the source tenant’s structure. However, any custom fields added by the destination tenant are preserved and never removed. The following rules explain how fields are added, reordered, or removed during upgrades:
|
Scenario |
Upgrade Result in Destination |
|---|---|
|
A new field is added in the source |
Added to the destination with all source properties. |
|
A Field is updated in the source |
Destination updated unless the field is flagged as Modified. |
|
Field deleted in the source (Locked/Partial) |
Deleted in the destination. |
|
Field deleted in the source (Unlocked) |
Deleted in the destination. |
|
Field deleted in the destination |
Recreated from the source on the next application upgrade. |
|
Field modified in the destination |
Preserved; source updates apply only if not overridden by the tenant. |