---
title: "The Appeals Dataset"
slug: "store-appeal-data-in-a-dataset"
updated: 2026-01-16T19:27:58Z
published: 2026-01-16T19:27:58Z
canonical: "knowledge.technolutions.net/store-appeal-data-in-a-dataset"
---

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

# The Appeals Dataset

Slate for Advancement databases are provisioned with an **Appeals**[**dataset**](/v1/docs/datasets-overview)**,**in which each record represents an appeal.

When creating gifts on a record, use the **autosuggest box** to find the appeal you want to use.

📖 [Appeals](/v1/docs/appeals)

**[![Autosuggest_Appeals.png](https://cdn.us.document360.io/cd8ea7a6-07f3-4846-a554-627ac016d3e3/Images/Documentation/autosuggest_appeals.png)](https://cdn.us.document360.io/cd8ea7a6-07f3-4846-a554-627ac016d3e3/Images/Documentation/autosuggest_appeals.png)**

## Creating an appeals dataset

Advancement offices have historically created prompt lists to store appeals data. However, if your process involves tracking a lot of data within each appeal, storing all that data in a prompt list can be cumbersome. To allow for the setting of additional data points and to improve reporting, you can now use an **appeal dataset** to store the appeal data.

If your institution has yet to set up appeals data in your database, setup is as simple as [setting up a fund](/v1/docs/funds-dataset) (another type of dataset record):

1. Go to **Database → Datasets.**
2. Select **Insert.**
3. Configure the following settings:
  - **Name:** Give your appeal a name, like `Appeal`.
  - **Type:**Enter****`gift_appeal`

[![Insert_New_Dataset_Record.png](https://cdn.us.document360.io/cd8ea7a6-07f3-4846-a554-627ac016d3e3/Images/Documentation/insert_new_dataset_record.png)](https://cdn.us.document360.io/cd8ea7a6-07f3-4846-a554-627ac016d3e3/Images/Documentation/insert_new_dataset_record.png)
4. Select **Save.**
5. Either manually or [via import](/v1/docs/upload-dataset-stages), add records to the dataset.

## Migrating existing appeals prompts to your new appeals dataset

For institutions already using appeals prompts, the appeals dataset is all or nothing: if a dataset with the `gift_appeal` type exists, **existing appeal prompts** **will not be used**.

Since your institution may already have gifts that use the appeals prompt list, we've created a query that you can [import into your database](/v1/docs/suitcase-import) that walks you through the migration process.

### Importing the migration query

> [!CAUTION]
> 🔔 Important!
> 
> Follow these steps in your [test environment](/v1/docs/test-environments) first to confirm the effects on your individual database before attempting in a production environment.

To import the query:

1. Copy the following **Suitcase ID**:

```SuitcaseID
a358facd-4f34-0b66-ea06-96b5c906238f@slate
```
2. Go to **Database → Suitcase Import.**
3. Paste the ID.
4. Select **Import.**

### Migrating the prompts

> [!NOTE]
> 💡 You can also find the following steps in the Suitcase query’s description in Slate.

To migrate appeals prompts:

1. Go to **Database → Datasets.**
2. Select **Insert.**
3. **Configure the following settings:**
  - **Name:** `Staging Appeal`

**Type:**`staging_appeal`
4. Select **Save.**
5. Go to the query you imported with Suitcase.
6. Select **Run Query.**The following occurs:
  - The query recreates all existing `gift_appeal` prompts as records in the new dataset.
  - The name of the record is set to the value of the prompt, and the active status of the record is set to the active status of the prompt.
  - If the prompt already exists based on the ID, it will be skipped—no need to worry if you accidentally run it more than once.
7. Perform any additional adjustments to the records either manually or [via import](/v1/docs/upload-dataset-stages).
8. When you're ready to transition to using the dataset instead of prompts, update the appeal dataset type to `gift_appeal` (replacing `staging_appeal`).

### Undoing the migration

If you followed the preceding steps and decide you aren't quite ready yet, you can undo the process:

1. In the new appeal dataset, set the **type** back to `staging_appeal`.
2. Use your appeal prompts.

The Suitcase process does not remove these prompts.

### Housekeeping

Once you've migrated your appeals prompts to the new appeals dataset, there are a few things to do to enjoy its benefits fully:

1. [Create a local query base for the appeals dataset](/v1/docs/custom-dataset-legacy-compatibility#step-3-add-the-custom-dataset-query-base). This allows you to create exports and filters.
2. Create the local exports and filters for [Lookup](/v1/docs/custom-dataset-legacy-compatibility#step-4-creating-the-lookup) and [Partial Match](/v1/docs/custom-dataset-legacy-compatibility#step-5-creating-the-partial-match), so the dataset appears in search results like other records.
3. Refresh the Configurable Joins library (**Database → Refresh Configurable Joins Library**) so that joins for the appeals dataset appear. This also happens automatically overnight.

### Mapping to appeals

In imports and forms, you may continue to use value mappings as before, but you'll also find an added destinations of **Appeal - Key** to which you may send the key of the dataset record.

[![Destination_-_Appeal_Key.png](https://cdn.us.document360.io/cd8ea7a6-07f3-4846-a554-627ac016d3e3/Images/Documentation/destination_-_appeal_key.png)](https://cdn.us.document360.io/cd8ea7a6-07f3-4846-a554-627ac016d3e3/Images/Documentation/destination_-_appeal_key.png)