> ## Documentation Index
> Fetch the complete documentation index at: https://docs.wegive.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Why a Salesforce Field Receives the Custom Field's Name Instead of Its Value

> If a mapped Salesforce field is filled with text like CF_123_my_field instead of the real value, the mapping rule has Static Value turned on. Here is how to fix it.

You mapped a WeGive custom field to a Salesforce field, but when you check the integration log (or the record in Salesforce) the Salesforce field contains the custom field's reference name, such as `CF_687_payment_platform`, instead of the donor's or gift's actual value.

## What is happening

Every mapping rule on **Settings > Integrations > Salesforce NPSP > Mapping Rules** has a **Static value (WeGive field is a literal)** checkbox. When it is ticked, WeGive does not look anything up. It sends exactly the text in the WeGive field box to Salesforce, every time. If that text is a custom field's reference name, Salesforce receives the name itself as a plain string.

Static Value is meant for fixed values, for example always sending `Online` to a "Source" field. A rule with Static Value ticked is also export-only (WeGive to Salesforce), so its direction switches to Export automatically.

## How to fix it

1. Go to **Settings > Integrations > Salesforce NPSP** and open the **Mapping Rules** tab.
2. Find the rule for the Salesforce field and click to edit it.
3. Untick **Static value (WeGive field is a literal)**. The label changes back from "Static Value" to the normal field box.
4. In the WeGive field box, enter the custom field's full reference name exactly as it appears in WeGive, including the number and the name, for example `CF_687_payment_platform`. The number alone (`CF_687`) is not enough for Salesforce rules. The reference name is shown where you manage the custom field; see [Custom Fields](https://docs.wegive.com/external/support/settings/custom-fields.md#api--reference-name-format).
5. Choose the direction you want (Both, Export, or Import) now that the direction is no longer locked, and save.

## What to expect after the fix

* The next push of a record sends the custom field's value. If a record has no value stored for that field, WeGive sends the custom field's default value instead.
* Records that were already pushed keep the wrong text in Salesforce until they are pushed again. A later edit to the record, or a re-sync, updates them.
* If you actually want to send the same fixed text on every record, leave Static Value ticked and type the exact value you want Salesforce to receive instead of a reference name.

If the field still shows the wrong value after these steps, contact WeGive support with the Salesforce field name and a recent integration log entry.


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