> For the complete documentation index, see [llms.txt](https://solutions.fundraisingbox.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://solutions.fundraisingbox.com/platform-solutions-integrations/salesforce-nonprofit-cloud-npc/business-processes/designations-donation-purposes.md).

# Designations / Donation Purposes

{% hint style="info" %}
The Project ID Code used in option 1-3 below typically represents a meaningful code or label used as a donation purpose, often already defined in an external system. 

The project name and Project ID Code can be identical. Information on creating ID codes in FundraisingBox is available [here](https://support.fundraisingbox.com/de/support/solutions/articles/79000145967-id-codes-anwendungsf%C3%A4lle-verwendung).

Once configured, the process runs automatically. No further action is required from the FundraisingBox project team, allowing designations and donation purpose mappings to be created and adjusted flexibly.
{% endhint %}

### **Option 1: Using an Existing Salesforce Gift Designation**

A designation can be linked by directly referencing an existing Gift Designation in Salesforce. To use this option:

* A Gift Designation has to be created in Salesforce.
* The Gift Designation ID (retrievable from the Salesforce URL) has to be used as the Project ID Code in FundraisingBox. 
* The Project ID Code is then linked to a project in FundraisingBox.

This project can subsequently be selected as a donation purpose within donation forms.

### **Option 2: Using a Unique Custom Field in Salesforce**

Alternatively, a designation can be mapped using a custom identifier. For this option:

* A custom field marked as 'unique' has to be created on the Gift Designation object in Salesforce.
* A new Gift Designation is created and assigned a value in this unique field.
* The same value is used as the Project ID Code in FundraisingBox. 

This allows flexible mapping without relying on Salesforce record IDs.

### **Option 3: Mapping via 'Donation Purpose' Field**

Another approach is to use preconfigured project mappings within FundraisingBox. In this case, the Project ID Code is transferred automatically:

* into the Gift Transaction (for one-time donations), or
* into the Gift Commitment (for recurring donations), where all subsequent transactions will carry the same value,
* or into the Campaign when created via a P2P fundraising campaign.

Each project created in FundraisingBox must be assigned a corresponding Project ID Code. 

***

### **Option 4: Mapping via Source ID Codes**

As an additional option, Source ID Codes (Information on creating ID codes in FundraisingBox is available [here](https://support.fundraisingbox.com/de/support/solutions/articles/79000145967-id-codes-anwendungsf%C3%A4lle-verwendung)) can be used. These are configured in FundraisingBox and assigned to:

* donation forms, or
* P2P fundraising campaigns.

The Source ID Code is then automatically transferred:

* into the Gift Transaction, or
* into the Gift Commitment (for recurring donations), where all follow-up donations inherit the same value.

After initial setup, this process is fully automated. This allows sources to be managed and adjusted flexibly without further involvement from the FundraisingBox project team.

***

### **Option 5: Using Transaction Custom Fields in FundraisingBox**

Designations can also be captured using custom fields defined in FundraisingBox. For this option:

* A transaction custom field must be created in FundraisingBox. Learn [here](https://support.fundraisingbox.com/de/support/solutions/articles/79000127361-benutzerdefinierte-felder-anlegen-bearbeiten-archivieren-oder-l%C3%B6schen) how to configure custom fields in FundraisingBox.
* The custom field must be activated in the donation form.

The value entered by the donor can then be transferred via the connector and used for designation mapping in Salesforce.

{% hint style="warning" %}
Values from custom fields are automatically written to the corresponding raw data field. Direct mapping to a specific Salesforce field requires commissioning the FundraisingBox project team.
{% endhint %}

<br>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://solutions.fundraisingbox.com/platform-solutions-integrations/salesforce-nonprofit-cloud-npc/business-processes/designations-donation-purposes.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.