Object and Field Reference

This page is a field-oriented companion to the object model. It does not list every field in the org. It explains the object contracts and the field families that developers, admins, and operators need to understand before changing data, automation, reports, or integrations.

Object Size Snapshot

The repo extends several objects heavily. Field count is a signal that the object is an operational contract, not a simple form.

Field Family Conventions

CRM and Activity

Best practices:

1. Use Task/Activity for sales touch data; do not create a parallel custom activity object.
2. Keep Lead rollup fields system-owned.
3. Add fields only when they support reporting, automation, or handoff. Do not use free-text notes for data that managers need to measure.
4. If a field is required in validation, put it on the quick action/layout where users enter the data.

Quotes and Quote Lines

Quote line contract:

Best practices:

1. Create and edit lines through the Line Items editor, not raw related-list creation.
2. Do not manually change approval fields to skip approval.
3. Clone/revise quotes instead of overwriting submitted or rejected history.
4. Treat quote-line margin and commission fields as calculated evidence unless the commission override workflow explicitly owns the change.

Sales Orders and Sales Order Lines

Sales Order line contract:

Best practices:

1. Use supported Sales Order actions for invoice, payment, tracking, cancellation, ownership, and recurring plans.
2. Do not edit lines casually after payment, invoice, tracking, or fulfillment evidence exists.
3. Use credit, reversal, cancellation, or admin repair paths instead of deleting financial history.
4. Keep external RMA context on Sales Orders as correlation only.

Payments

Best practices:

1. Do not create fake transactions or receipts to make reports balance.
2. Use idempotency and gateway lifecycle fields as evidence, not as retry toggles.
3. Gateway changes are migration work. Use successor-backed lifecycle changes, token coverage checks, and historical transaction preservation.
4. Billing/shipping snapshots on payment records are historical evidence. Correct the source customer/address for future payments instead of overwriting old snapshots.

3PL and Fulfillment

Best practices:

1. Diagnose provider sync using runtime request, transaction, sync state, and history together.
2. Missing tracking is not proof of missing fulfillment. Check shipped-line and external fulfillment evidence first.
3. Provider warehouse deactivation requires successor-backed handoff and blocker review.
4. Provider-owned inventory should be mirrored from provider systems, not manually edited as internal stock.

Items, Inventory, BOM, and Purchasing

Best practices:

1. Use Item Manager and item creation wizard for setup; raw item creation misses policy and setup warnings.
2. Do not sell or quote items with setup blockers just because a line can be forced in.
3. Use structured inventory adjustments with reason/reference, not direct quantity edits.
4. Treat BOM/cost fields as finance-impacting, not cosmetic product data.

Finance and Commissions

Best practices:

1. Use GL Intelligence to repair missing defaults rather than hand-maintaining one-off rules.
2. Keep financial audit records. They are not disposable logs.
3. Commission reports should be read with payment, refund, dispute, cancellation, and margin context.

Change Control Rules

1. Before editing a field, identify whether it is user-entered, calculated, imported, integration-owned, or historical snapshot.
2. Before adding a new field, identify its owner, entry surface, reporting purpose, permission coverage, and cleanup/retention impact.
3. Before changing picklist values, check reports, dashboards, validation rules, Apex services, LWCs, and integrations.
4. Before changing statuses, check automation that uses the status as a gate.
5. Before changing object relationships, check delete behavior, sharing/access, rollups, and existing historical records.
6. Before changing payment, fulfillment, or finance fields, define a migration path and rollback path.