Field Configuration

How fields, field order and field-level updates work.

Fields are based on the live HighLevel object schema. Every time the form is opened or reloaded, the app retrieves:

  • the current object schema
  • the current CRM record values
If an administrator changes the object's fields while a user already has a form open, that open form will not see those changes until it is reloaded.

Field Order

Fields follow the order configured natively in HighLevel for custom fields. No separate field-order configuration is required in Update Records with Forms.

Field-level Updates

The app performs field-specific updates. Only values actually changed on the form are written back to HighLevel.

Example: a customer opens a record containing Name, Phone, Email and Address. They change only the phone number. The app writes only the changed phone field back to HighLevel rather than rewriting the whole record.

Concurrent Editing

If two users modify different fields, both changes can survive.

Example: User A changes Phone. User B changes Address. Both updates can be retained because only changed fields are written.

If two users modify the same field, the most recent successful save wins.