All topics
English

Module fields · 2 min read

Validate fields, languages and integrations

Review the setup and troubleshoot without recreating fields or exposing data.

In this guide
  1. Check with representative staff
  2. Custom content is not automatically translated
  3. Protect data and check integration mappings
  4. Common problems
  5. Related guides

For Insurance agency Owners and administrators.

Check with representative staff

  • Definition belongs to the correct module and organization.
  • API name, type, section and options confirmed after reopening.
  • A test record preserves values after saving.
  • Required data is understandable and available at creation time.
  • Hidden, inactive and field permissions produce the intended result.
  • Filters and related processes have been reviewed.
  • Portuguese-, English- and Spanish-speaking users understand labels and instructions.
Module selection: Contacts, Accounts, Tasks/Kanban, Deals or Policies.
Module selection: Contacts, Accounts, Tasks/Kanban, Deals or Policies. Open the image to enlarge it.

Custom content is not automatically translated

Agency-entered labels, descriptions, sections and options are displayed literally. This editor does not offer three translations per field. Product controls and standard types follow the user’s language; switching language does not translate your configuration.

Agree on shared vocabulary, such as Pending / Pendente / Pendiente where needed. Keep the API name stable and avoid three separate fields for one fact in three languages. In this manual, translated examples were entered separately in each demonstration environment.

Protect data and check integration mappings

Use field security and sensitive-data controls for profile restrictions. Do not store full SSNs, passwords or card information in ordinary fields. Additional contact data can synchronize with the conversation service; other modules retain their own local values.

A new field called NPN or status does not change policy import contracts. Confirm API names and supported mappings for integrations. Do not rename used options without reviewing filters, processes and old data.

Common problems

ProblemCheck
Module missing from selectionPlan, activation and access. See the Modules chapter.
Duplicate or reserved API nameReview existing definitions and choose an appropriate key.
Save field is unavailableWait for sections to load, or finish/cancel inline section creation.
Field missing on a recordCorrect module, active, visible, loading and permissions.
Cannot change type or API nameThe editor locks these after creation; plan another field if needed.
Option rejected or record will not saveCurrent option list, required values and data format.

Give support the organization, module, API name, expected behavior and error. Use screenshots without personal information. See Modules for availability issues.

Related guides

Updated October 25, 2026.