Simple Object Designer Documentation
Index

Force Mode

Force mode (Force Sync) allows publishing changes that would normally be blocked due to potential data loss. This page explains when and how to use force mode.

What is Force Mode

Force mode sets the Publish Update Mode to "Force Sync", which:

  • Allows destructive schema changes
  • Bypasses normal data protection
  • Enables field removal and type changes
  • May result in data loss

What Force Sync does not do

Force Sync affects schema synchronization during deployment only. It is not a general "make it publish" switch, and two limits catch people out:

  • It does not fix compilation errors. If a deleted field is still referenced by an API page or a page placement, publishing fails at compilation with AL0132: 'Record "…"' does not contain a definition for '<FieldName>' — with or without Force Sync.
  • It does not clean up references. Removing a field from pages, reports and API endpoints is a manual step in SOD.

Before force-publishing a field removal, remove the field from every page placement, report placement and API endpoint. See Create New Fields for the order of operations and Publishing Failures for the uninstall + Refresh Symbols (with cache clearing) recovery procedure.

In Dual-App mode, also uninstall App 2 before republishing — see Dual-App Deployment.

When Force Mode is Needed

Removing Fields

When you remove a field that contains data:

  • Normal sync blocks the change
  • Force mode allows removal
  • Data in that field is lost

Changing Field Types

When changing a field to incompatible type:

  • Integer to Text
  • Decimal to Boolean
  • Changes that can't preserve data

Removing Features

When deleting entire feature tables:

  • Table and data removed
  • All records deleted

Schema Restructuring

Major changes to table structure:

  • Key changes
  • Relationship modifications

Enabling Force Mode

In Setup

  1. Open Setup page
  2. Find Publish Update Mode
  3. Change from "Synchronize" to "Force Sync"
  4. Publish your changes
  5. Important: Change back to "Synchronize" after

Publish Update Mode Values

Mode Behavior
Add app to manifest Registers the app without running schema sync
Synchronize Normal mode, protects data
Force Sync Force mode, allows data loss

Data Loss Scenarios

Field Removal

Before Force:

Customer Table:
- No.
- Name
- Custom Field (contains data)

After Force (field removed):

Customer Table:
- No.
- Name
(Custom Field and its data are gone)

Feature Deletion

Before Force:

Equipment Table: 50 records
Equipment List Page

After Force (feature deleted):

(Everything gone - table, page, all 50 records)

Safety Procedures

Before Using Force Mode

  1. Backup data - Export affected data
  2. Document changes - Know what will be lost
  3. Verify intent - Confirm deletion is desired
  4. Test in sandbox - Try force mode in non-production first

Data Backup Methods

Export data before force operations:

  • Excel export from lists
  • Configuration packages
  • Database backup (if accessible)

After Using Force Mode

  1. Change back - Set mode to Synchronize
  2. Verify - Check expected changes occurred
  3. Test - Confirm system works correctly
  4. Document - Record what was changed

Common Force Mode Scenarios

Cleanup Old Fields

Removing fields no longer needed:

  1. Verify field is truly unused
  2. Export any needed data
  3. Remove field from SOD
  4. Enable Force Sync
  5. Publish
  6. Disable Force Sync

Restructuring Features

Major feature changes:

  1. Export all feature data
  2. Delete feature
  3. Enable Force Sync
  4. Publish
  5. Disable Force Sync
  6. Create new feature structure
  7. Publish (normal mode)
  8. Import data to new structure

Fixing Mistakes

If you created something incorrectly:

  1. Assess what needs to change
  2. Determine if force is needed
  3. Backup if data exists
  4. Make corrections
  5. Force publish if required
  6. Return to normal mode

Risks of Force Mode

Data Loss

Primary risk:

  • Data is permanently deleted
  • No automatic recovery
  • Must restore from backups

User Impact

During force operations:

  • Users may see errors
  • Data disappears
  • Confusion and support requests

Audit Concerns

Force changes:

  • May affect compliance
  • Should be documented
  • Consider approval process

Alternatives to Force Mode

Instead of Removing Fields

  • Mark as hidden
  • Stop using (but keep)
  • Rename with "obsolete" prefix

Instead of Changing Types

  • Create new field with correct type
  • Migrate data manually
  • Remove old field later

Planning Ahead

Avoid force mode by:

  • Careful initial design
  • Testing in sandbox
  • Incremental changes

Best Practices

Minimize Force Usage

  • Use only when necessary
  • Plan to avoid force scenarios
  • Consider alternatives

Always Backup

Before any force operation:

  • Export affected data
  • Have recovery plan
  • Test backup validity

Document Everything

Record:

  • What was force-published
  • When it occurred
  • What data was affected
  • Who authorized it

Return to Normal

Always:

  1. Complete force operations
  2. Verify results
  3. Change back to Synchronize
  4. Never leave in Force Sync permanently