> ## 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.

# How to Set a Designation's Salesforce ID (and Why You Can't Edit It on the Designation Page)

> Why the Salesforce ID on a designation is read-only in the dashboard, where it comes from, and how to set it yourself with the Import Wizard's Update action on Funds, including how to link your General Fund to an existing Salesforce GAU before your first sync so you don't end up with duplicates.

## Overview

Each designation can carry a **Salesforce ID**, the ID of the matching General
Accounting Unit (GAU) in Salesforce. WeGive uses it to send gifts to the right
GAU and to match GAUs coming back from Salesforce.

You can see the Salesforce ID on a designation's detail page, but you can't
change it on the **Edit Designation** page. The field isn't offered there on
purpose: the ID is normally filled in automatically by the Salesforce sync.

You can set it yourself with the Import Wizard, as described below.

## Where the ID normally comes from

* **A designation created in WeGive:** when a gift to it is synced, WeGive
  creates a matching GAU in Salesforce and saves that GAU's ID on the
  designation.
* **A GAU created in Salesforce:** when WeGive pulls GAUs from Salesforce, each
  one is matched to a designation by Salesforce ID. A GAU that doesn't match
  any existing designation creates a new designation in WeGive. WeGive does not
  match on the name.

## Set the Salesforce ID with the Import Wizard

Use this when a designation already exists in WeGive and you want to tie it to
a GAU that already exists in Salesforce.

1. Build a CSV with one row per designation. Include a column that identifies
   the designation, either its **WeGive ID** (best) or its **Name**, and a column
   with the GAU's **Salesforce ID**. Copy the ID from Salesforce exactly as it
   appears (the 18-character ID is safest).
2. Go to **Data > Imports** and click **+** to start a new import.
3. Choose the **Update** action and the **Fund** object type (designations are
   called Funds in the Import Wizard).
4. Upload your CSV.
5. Map the identifier column to **WeGive ID** or **Name**, and map the ID column
   to **Salesforce ID**. (Organizations that use NPC can map **NPC ID** the same
   way.)
6. Set **Primary Identifier** to the identifier you mapped in step 5.
7. Run the import, then download the results file to check for row errors.

What to expect:

* Update never creates designations. A row that matches nothing fails with
  "Fund does not exist", and a row that matches more than one designation (for
  example, two with the same name) fails with "Multiple funds found". Use the
  WeGive ID to avoid this.
* Only cells with a value are written. A blank Salesforce ID cell leaves the
  existing ID unchanged, so an import can't be used to clear an ID.
* Once the ID is saved, WeGive treats the designation as already linked: later
  syncs update that GAU instead of creating a new one.

## Link your General Fund before the first sync

Every new account starts with a **General Fund** that has no Salesforce ID.
If your Salesforce already has a General Fund GAU and you sync before linking
them, WeGive can create a second GAU in Salesforce for gifts to the General
Fund, and can create a second designation in WeGive when it pulls your
existing GAU.

To avoid that, run the import above for your General Fund (and any other
designations that already have GAUs) **before** your first sync or first
synced gift. If a duplicate has already been created, contact WeGive Support
so it can be cleaned up.

## Related articles

* [Designations in WeGive (Dashboard v2)](https://docs.wegive.com/external/support/giving/designations-in-wegive-dashboard-v2.md)
* [How the Salesforce Sync Works](https://docs.wegive.com/external/support/integrations/how-the-salesforce-sync-works.md)
* [Updating Existing Payments with the Import Wizard](https://docs.wegive.com/external/support/giving/updating-existing-payments-with-the-import-wizard.md)


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