{"title":"Resolve required field sync errors","slug":"resolve-required-field-sync-errors","url":"https://support.storeconnect.com/articles/resolve-required-field-sync-errors","url_markdown":"https://support.storeconnect.com/articles/resolve-required-field-sync-errors.md","subtitle":null,"summary":"Fix REQUIRED_FIELD_MISSING sync errors caused by Salesforce field-level Required settings blocking the StoreConnect sync user from creating or updating records.","type":"Help_Documentation","video_url":"","keywords":"REQUIRED_FIELD_MISSING, required field, field-level required, validation rule, sync error, sync user, profile exclusion","last_modified":"2026-08-21T07:12:35+0000","body_markdown":"## Symptoms\n\nYou see a sync error in the [sync error tool](sync-error-tool) with the status code **REQUIRED_FIELD_MISSING** and a message identifying the field that could not be saved. For example:\n\n- `Required fields are missing: [Type__c]`\n- `Required fields are missing: [Customfield__c]`\n\nThe error always names the specific field that the sync user was unable to populate.\n\n## Cause\n\nWhen 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.\n\nThis 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.\n\nField-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.\n\n## Resolution\n\nYou 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.\n\n### Step 1: Identify the affected field and record\n\n1. Open the [sync error tool](sync-error-tool) and filter by the affected object (for example, Contact or Account).\n2. Read the error message to identify which field is marked as Required.\n3. Note the **Salesforce ID** from the error detail and use it to locate the affected record.\n4. 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.\n\n:::tip\nSelect 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.\n:::\n\n### Step 2: Remove field-level Required\n\n1. In Salesforce, go to **Setup \u003e Object Manager**.\n2. Select the object named in the sync error (for example, Contact).\n3. Go to **Fields \u0026 Relationships** and open the field named in the error message.\n4. Click **Edit**.\n5. Uncheck the **Required** checkbox.\n6. Click **Save**.\n\n:::warning\nUnchecking Required removes the enforcement for all users immediately. Complete Step 3 before leaving the field unprotected.\n:::\n\n### Step 3: Create a Validation Rule with a sync user exclusion\n\n1. In **Object Manager**, select the same object.\n2. Go to **Validation Rules** and click **New**.\n3. Enter a **Rule Name** (for example, `Require_Type_Except_Sync_User`).\n4. In the **Error Condition Formula**, use one of the following options to exclude the sync user from the required field check.\n\n#### Option A: Exclude by profile\n\nThis excludes all users assigned to the sync user's profile. Use this when the profile is dedicated to the **StoreConnect Sync User**.\n\nTo find the profile name, go to **Setup \u003e Users**, open the **StoreConnect Sync User**, and note the value in the **Profile** field.\n\n```\nAND(\n  ISBLANK(Customfield__c),\n  $Profile.Name \u003c\u003e \"Salesforce API Only System Integrations\"\n)\n```\n\n:::note\nThe 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 \u003e Users** before saving the rule. See [Set up a StoreConnect sync user](how-to-create-a-storeconnect-sync-user) for details on how the sync user is configured.\n:::\n\n#### Option B: Exclude by username\n\nThis excludes only the specific sync user. Use this when other users share the same profile and you only want to exclude the sync user.\n\nTo find the username, go to **Setup \u003e 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](how-to-create-a-storeconnect-sync-user) for details on identifying this user.\n\n```\nAND(\n  ISBLANK(Customfield__c),\n  $User.Username \u003c\u003e \"storeconnect.syncuser@example.com\"\n)\n```\n\n5. Enter an **Error Message** (for example, \"This field is required.\").\n6. Select **Field** next to \"Error Location\" and choose the field so the error appears next to it on the page layout.\n7. Click **Save**.\n8. Verify the rule is **Active**.\n\nReplace `Customfield__c` in the formula with the field API name from your sync error message.\n\n### Step 4: Re-sync affected records\n\n1. Return to the [sync error tool](sync-error-tool).\n2. Select all affected records for the object.\n3. Click **Re-sync**.\n\n## Verification\n\n1. Confirm the sync error no longer appears in the [sync error tool](sync-error-tool).\n2. Open the synced record in Salesforce and verify it was created or updated correctly.\n3. 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.\n\n## Prevention\n\n- **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.\n- **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.\n- **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.\n- **Monitor the [sync error tool](sync-error-tool)** after making changes to field definitions or adding new required fields.\n\n## Related issues\n\n- [Manage sync errors](sync-error-tool)\n- [Resolving custom validation sync errors](resolve-custom-validation-sync-errors)\n- [How to find and resolve sync errors](how-to-find-and-resolve-sync-errors)\n- [How to create a StoreConnect Sync User](how-to-create-a-storeconnect-sync-user)"}