Warnings in Salesforce Setup flag a configuration that may fail, but not all of them block saving. Open the icon's tooltip to read the reason before changing the mapping.

What each icon means

Visible icon	What it actually means
`Enginy overwrites Salesforce`	Enginy can replace the existing value during an export.
`Sync with Salesforce`	On existing records, Enginy keeps non-empty values and fills in empty ones. It is not an automatic import.
Yellow warning	There is a possible type or options problem. The warning does not block saving.
Red circle with an x	The option is disabled. Hover to see the reason.
Blue check	This is the field selected in the dropdown. It does not confirm that the mapping is valid.

Important: Enginy does not receive all the metadata needed to identify every read-only Salesforce field in advance. A field with no red icon can still fail because of permissions, schema restrictions or organization rules.

Field type warnings

Enginy compares the type of the source value with the type of the Salesforce field.

Salesforce type	Expected use
string, textarea, email, phone, url	Text
int, double, currency, percent	Number
date, datetime	Date
boolean	True or false value
picklist, multipicklist	Options defined in Salesforce
reference	Reference to another record

Salesforce can reject the value even when Enginy lets you save the mapping.

Selecting a field also does not confirm that the connected user can edit it.

Check in Salesforce: object permissions, Field-Level Security, that the field can be filled in on create or update, and applicable Record Types and Validation Rules.

Picklists and multipicklists

A Picklist only accepts the values defined in Salesforce. The value sent must match a valid option.

When Enginy shows an options selector in Fixed value fields or Engagement fields, choose one of the available values. Avoid typing a similar label or a different translation.

A restricted Picklist can reject any value that is not allowed. Also check whether the options change depending on the Record Type.

Duplicate warnings

In Sync Configuration you will find Create/Update records on duplicate warnings.

This option is off by default and is labeled Not recommended.

Turning it on asks Salesforce to allow saving when a Duplicate Rule returns a warning. It does not turn off Enginy's matching and does not bypass other Salesforce controls.

The option does not let you skip:

Validation Rules.
Required fields.
Field-Level Security.
Object permissions.
Record Type restrictions.
Duplicate Rules configured to block the operation.

Turn it on only if your Salesforce administrator has confirmed that creating or updating despite the warning is acceptable.

Common Salesforce errors

Code or message	What to check
`REQUIRED_FIELD_MISSING`	Required standard or custom fields with no value.
`INVALID_OR_NULL_FOR_RESTRICTED_PICKLIST`	The value does not exist in the Picklist or is not available for the Record Type.
`INVALID_FIELD` or `No such column`	The API name changed, the field was deleted, or the user cannot query it.
`INSUFFICIENT_ACCESS`	Object permissions, Field-Level Security, sharing rules or Owner.
`FIELD_CUSTOM_VALIDATION_EXCEPTION`	A Validation Rule rejected the value.
`DUPLICATES_DETECTED`	A Salesforce Duplicate Rule blocked or warned about the operation.
`INVALID_CROSS_REFERENCE_KEY`	The ID of a relationship or Owner is invalid or not accessible.
`INVALID_SESSION_ID`	The session expired. Use `Reconnect`.
`REQUEST_LIMIT_EXCEEDED`	The organization has temporarily reached its API limit.

Required fields

Check that Enginy sends the necessary standard fields: LastName for Contact, Name for Account, and LastName and Company for Lead.

Your organization may add other required fields through configuration, Record Types or Validation Rules.

You can supply those values through Field Mapping, Fixed value fields or Manual export fields.

Permission errors

The user who connected Salesforce needs API Enabled and access to the objects in use.

Depending on the features you use, review:

Read, Create and Edit on Contact, Lead and Account.
Read on User to load Owners.
Create on Task to log conversations.
Access to Reports and List Views, along with the records they contain.
Read and write Field-Level Security for every mapped field.

The api, refresh_token and offline_access OAuth scopes keep the connection alive, but on their own they do not grant object or field permissions.

Choosing a different Owner does not change permissions either. Enginy still uses the connection of the user who authorized Salesforce.

Updating deleted or renamed fields

Open Salesforce under Integrations.
Click Configure.
In Salesforce Setup, click Refresh.
Review Field Mapping and Campaign Mapping.
Replace any fields that are no longer available.
Save your changes.

Review the Contacts, Leads and Companies tabs separately.

Salesforce authentication expired

If you see Salesforce authentication expired:

Open Integrations.
Find Salesforce.
Click Reconnect.
Authorize the connection again.
If you use My Domain, enter the correct Login URL.

Reconnecting the same integration keeps your configuration and mappings. You do not need to use Disable Salesforce to renew an expired session.

Errors importing Reports or List Views

If a Report fails validation, check that it contains records of the expected object, that the object matches Contact, Lead or Account, that the connected user can open the Report and read the records, and that Default object when exporting matches the type of contacts you want to import.

If a List View does not appear, check that the connected user can see it and that it contains detectable records.

Reviewing the Export Report

Open the export activity.
Go to Export Report.
Expand the failing record.
Read the user-facing message and the technical message.
Use Open in CRM if the report offers a link to the record.

What to send to support

Include this information:

Your Enginy workspace name.
The email of the user who started the operation.
Date, time and time zone of the error.
The operation affected and the object: Contact, Lead, Account or Task.
Approximate number of records.
The List View or Report name, if it was an import.
The Salesforce Record ID or link, if there is one.
The Enginy field and the Salesforce API name involved.
A full screenshot of the error.
The technical message from Export Report.
The Login URL used, stating whether it is production, My Domain.

Do not send passwords, access tokens, refresh tokens or Connected App secrets.

Troubleshoot Salesforce integration warnings and errors