> ## Documentation Index
> Fetch the complete documentation index at: https://unify-19-preview.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# Default values

> Fill empty Salesforce fields during sync.

export const ThemedImageFrame = ({lightSrc, darkSrc, alt, caption}) => <Frame caption={caption}>
    <img className="block w-full dark:hidden" src={lightSrc} alt={(alt ?? caption) ?? ""} />
    <img className="hidden w-full dark:block" src={darkSrc} alt={(alt ?? caption) ?? ""} />
  </Frame>;

## Overview

Default values provide a fallback when a mapped Unify value is missing. Use them
to populate required Salesforce fields or supply a consistent value for records
created through Unify, such as a description of where they came from.

Defaults apply to [mapped sync writes](/reference/integrations/salesforce/bidirectional-syncs#syncing-changes-to-salesforce).
They can populate a new record or fill an empty field on an existing record.
Existing Salesforce values are preserved when a default is applied.

## Set default values

You need permission to manage the Salesforce integration in Unify.

<Steps titleSize="h3">
  <Step title="Open the object mapping">
    Open [Settings → Salesforce](https://app.unifygtm.com/dashboard/settings/integrations/salesforce)
    and select the connection. Under **Field mappings**, click **Edit mapping**
    for the object whose defaults you want to configure.
  </Step>

  <Step title="Add a default">
    In **Set default values**, click **Add value**. Choose a Salesforce field
    and enter its default value. Use a value that matches the field's type
    and allowed options.

    For example, set Account Description to “Prospected in Unify.” This supplies a
    description when neither the mapped Unify value nor the existing Salesforce
    record provides one.

    <ThemedImageFrame lightSrc="/images/reference/integrations/salesforce/salesforce-default-values-light.png" darkSrc="/images/reference/integrations/salesforce/salesforce-default-values-dark.png" alt="Salesforce mapping editor with a description default set to Prospected in Unify." />
  </Step>

  <Step title="Save the defaults">
    Click **Save**. Subsequent mapped syncs use these defaults when a value is
    needed. Review a relevant write in **Sync log** to see the values sent to
    Salesforce.
  </Step>
</Steps>

## How values are chosen

A mapped Unify value takes precedence over a default. If no mapped value is
available, a default supplied by a play's sync action takes precedence over the
default configured in integration settings. Defaults fill empty destination
fields; the mapping's write behavior controls whether mapped values can replace
existing values.

Updates requested in chat use the values you ask chat to write.

See [Field mappings](/reference/integrations/salesforce/field-mappings#write-behavior)
for write behaviors and the [play action reference](/reference/plays/actions#sync-to-salesforce)
for action-specific values.

## Troubleshooting

<AccordionGroup>
  <Accordion title="Why wasn't my default used?">
    Check whether Salesforce already had a value or the mapped Unify attribute
    supplied one. Also review any values configured on the play action that
    performed the sync. Open the write in **Sync log** to inspect the result.
  </Accordion>

  <Accordion title="Why can't I select a field or save its value?">
    The field must exist on the selected Salesforce object and support writing
    a default. Check the connected account's permissions and the field's type.
    For a dropdown, use an allowed option; for a number or date, use the matching
    value type.
  </Accordion>
</AccordionGroup>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.