Resolve required field sync errors
On this page
You may have a field sync error if you see a sync error in the Manage sync errors with the status code REQUIRED_FIELD_MISSING and a message identifying the field that could not be saved. Examples include:
- “Required fields are missing: [Type__c]
- “Required fields are missing: [Customfield__c]””
The error always names the specific field that the sync user was unable to populate.
Cause of field sync errors
When StoreConnect’s sync creates or updates a record in Salesforce, the sync user must provide values for every field marked as Required at the field definition level. If the sync user does not have a value for one of these fields, Salesforce rejects the entire record save and raises a REQUIRED_FIELD_MISSING error.
This happens because Salesforce enforces field-level Required universally. It applies to every save operation on the object, regardless of whether the save comes from a manual user in the UI, an API call, or a managed package like StoreConnect. The sync user cannot populate fields outside of the data StoreConnect is designed to send, so any field marked as Required that StoreConnect does not map will block the sync.
Field-level Required cannot be bypassed. It has no conditional logic, no user exclusions, and no exceptions. If the checkbox is checked, every save operation on that object must include a value for the field. The fix is to replace the field-level Required setting with a Validation Rule, which supports conditional logic and allows you to exclude the StoreConnect Sync User profile or its Salesforce user while keeping the field effectively required for all other users.
Resolution for field sync errors
You cannot fix this error by adding a Validation Rule alone. A Validation Rule cannot override a field-level Required setting. You must first remove the field-level Required setting, then replace it with a Validation Rule that excludes the sync user.
Step 1: Identify the affected field and record
- Open the Manage sync errors and filter by the affected object (for example, Contact or Account).
- Read the error message to identify which field is marked as Required.
- Note the Salesforce ID from the error detail and use it to locate the affected record.
- If you see multiple errors for the same record, find the earliest error in the list. This is the initial sync failure that is blocking subsequent updates from processing.
:::tip Select all records for the same Salesforce ID when re-syncing, not just the most recent error. Earlier failed events for the same record may also need to be re-processed. :::
Step 2: Remove field-level Required
- In Salesforce, go to Setup > Object Manager.
- Select the object named in the sync error (for example, Contact).
- Go to Fields & Relationships and open the field named in the error message.
- Click Edit.
- Uncheck the Required checkbox.
- Click Save.
:::warning Unchecking Required removes the enforcement for all users immediately. Complete Step 3 before leaving the field unprotected. :::
Step 3: Create a Validation Rule with a sync user exclusion
- In Object Manager, select the same object.
- Go to Validation Rules and click New.
- Enter a Rule Name (for example,
Require_Type_Except_Sync_User). - In the Error Condition Formula, use one of the following options to exclude the sync user from the required field check.
Option A: Exclude by profile
This excludes all users assigned to the sync user’s profile. Use this when the profile is dedicated to the StoreConnect Sync User.
To find the profile name, go to Setup > Users, open the StoreConnect Sync User, and note the value in the Profile field.
AND(
ISBLANK(Customfield__c),
$Profile.Name <> "Salesforce API Only System Integrations"
)
:::note
The examples above use Salesforce API Only System Integrations, but your org may use a different profile. Always verify the exact profile name from the sync user’s record in Setup > Users before saving the rule. See Set up a StoreConnect sync user for details on how the sync user is configured.
:::
Option B: Exclude by username
This excludes only the specific sync user. Use this when other users share the same profile and you only want to exclude the sync user.
To find the username, go to Setup > Users and locate the user configured for StoreConnect sync. The Username column shows the value to use in the formula. See Set up a StoreConnect sync user for details on identifying this user.
AND(
ISBLANK(Customfield__c),
$User.Username <> "storeconnect.syncuser@example.com"
)
- Enter an Error Message (for example, “This field is required.”).
- Select Field next to “Error Location” and choose the field so the error appears next to it on the page layout.
- Click Save.
- Verify the rule is Active.
Replace Customfield__c in the formula with the field API name from your sync error message.
Step 4: Re-sync affected records
- Return to the Manage sync errors.
- Select all affected records for the object.
- Click Re-sync.
Verify the fix
- Confirm the sync error no longer appears in the Manage sync errors.
- Open the synced record in Salesforce and verify it was created or updated correctly.
- Test that the Validation Rule works for manual users by attempting to save a record with the field left blank from the Salesforce UI. You should see the validation error message.
Prevention
- Audit Required fields on synced objects (Account, Contact, Order) and replace field-level Required settings with Validation Rules that exclude the sync user profile where appropriate.
- Use Validation Rules instead of field-level Required for any field that the sync user does not populate. This gives you conditional control over enforcement.
- Check field settings when adding new custom fields to synced objects. If a new field is marked as Required and StoreConnect does not map it, sync errors will occur as soon as records are created or updated.
- Monitor the Manage sync errors after making changes to field definitions or adding new required fields.